home.social

#psutil — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #psutil, aggregated by home.social.

  1. Ah yes, nothing says "cutting-edge tech" like freethreaded Python wheels for #psutil. 🤓 Let's gather the entire Python community to celebrate this riveting achievement of compiling some C code and throwing it into a wheel like it's 1998. 🎉 Bravo, dear developers—yet another feature that will change everything (or nothing).
    gmpy.dev/blog/2025/wheels-for- #PythonCommunity #TechNews #CCode #Innovation #Celebration #HackerNews #ngated

  2. Ah yes, nothing says "cutting-edge tech" like freethreaded Python wheels for #psutil. 🤓 Let's gather the entire Python community to celebrate this riveting achievement of compiling some C code and throwing it into a wheel like it's 1998. 🎉 Bravo, dear developers—yet another feature that will change everything (or nothing).
    gmpy.dev/blog/2025/wheels-for- #PythonCommunity #TechNews #CCode #Innovation #Celebration #HackerNews #ngated

  3. Ah yes, nothing says "cutting-edge tech" like freethreaded Python wheels for #psutil. 🤓 Let's gather the entire Python community to celebrate this riveting achievement of compiling some C code and throwing it into a wheel like it's 1998. 🎉 Bravo, dear developers—yet another feature that will change everything (or nothing).
    gmpy.dev/blog/2025/wheels-for- #PythonCommunity #TechNews #CCode #Innovation #Celebration #HackerNews #ngated

  4. Ah yes, nothing says "cutting-edge tech" like freethreaded Python wheels for #psutil. 🤓 Let's gather the entire Python community to celebrate this riveting achievement of compiling some C code and throwing it into a wheel like it's 1998. 🎉 Bravo, dear developers—yet another feature that will change everything (or nothing).
    gmpy.dev/blog/2025/wheels-for- #PythonCommunity #TechNews #CCode #Innovation #Celebration #HackerNews #ngated

  5. I want to measure run time of a Python program and compare it to /usr/bin/time. The script, t.py:

    import psutil, time,
    startSecs = psutil.Process(os.getpid()).create_time()
    print("startup took %.3fs" % (time.time() - startSecs))

    run as:

    /usr/bin/time -f 'wall=%e' python3 t.py

    output:

    startup took 0.822s
    wall=0.03

    where 0.8s is quite obviously wrong, not only because of the wall=0.03, but because there is no noticeable wait of nearly a second. How come?

    #python #programming #shell #psutil

  6. I want to measure run time of a Python program and compare it to /usr/bin/time. The script, t.py:

    import psutil, time,
    startSecs = psutil.Process(os.getpid()).create_time()
    print("startup took %.3fs" % (time.time() - startSecs))

    run as:

    /usr/bin/time -f 'wall=%e' python3 t.py

    output:

    startup took 0.822s
    wall=0.03

    where 0.8s is quite obviously wrong, not only because of the wall=0.03, but because there is no noticeable wait of nearly a second. How come?

    #python #programming #shell #psutil

  7. I want to measure run time of a Python program and compare it to /usr/bin/time. The script, t.py:

    import psutil, time,
    startSecs = psutil.Process(os.getpid()).create_time()
    print("startup took %.3fs" % (time.time() - startSecs))

    run as:

    /usr/bin/time -f 'wall=%e' python3 t.py

    output:

    startup took 0.822s
    wall=0.03

    where 0.8s is quite obviously wrong, not only because of the wall=0.03, but because there is no noticeable wait of nearly a second. How come?

    #python #programming #shell #psutil

  8. I want to measure run time of a Python program and compare it to /usr/bin/time. The script, t.py:

    import psutil, time,
    startSecs = psutil.Process(os.getpid()).create_time()
    print("startup took %.3fs" % (time.time() - startSecs))

    run as:

    /usr/bin/time -f 'wall=%e' python3 t.py

    output:

    startup took 0.822s
    wall=0.03

    where 0.8s is quite obviously wrong, not only because of the wall=0.03, but because there is no noticeable wait of nearly a second. How come?

    #python #programming #shell #psutil

  9. I want to measure run time of a Python program and compare it to /usr/bin/time. The script, t.py:

    import psutil, time,
    startSecs = psutil.Process(os.getpid()).create_time()
    print("startup took %.3fs" % (time.time() - startSecs))

    run as:

    /usr/bin/time -f 'wall=%e' python3 t.py

    output:

    startup took 0.822s
    wall=0.03

    where 0.8s is quite obviously wrong, not only because of the wall=0.03, but because there is no noticeable wait of nearly a second. How come?

    #python #programming #shell #psutil