psutil-7.1.2 (Python module)

[Bruce Dubbs]

New point version.

[Bruce Dubbs]

7.1.1 - 2025-10-19

Enhancements

• [SunOS]: dropped support for SunOS 10.
• [SunOS]: add CI test runner for SunOS.

Bug fixes

• [SunOS]: cannot compile psutil from sources due to missing C include.
• [SunOS]: Process.cmdline()_ does not handle spaces properly.

Compatibility notes

• SunOS 10 is no longer supported.

[Bruce Dubbs]

Fixed at commits

bade117777 Update to gc-8.2.10.
b145aa44f0 Update to stunnel-5.76.
ca8025eb52 Update to librsvg-2.61.2.
869e7d0bc0 Update to psutil-7.1.1 (Python module).

[Bruce Dubbs]

Now version 7.1.2.

7.1.2 - 2025-10-25

Enhancements

• stop publishing prebuilt Linux and Windows wheels for 32-bit Python. 32-bit CPython is still supported, but psutil must now be built from source.
• produce wheels for free-thread cPython 3.13 and 3.14

Bug fixes

• [macOS]: Process.cmdline()_ and Process.environ()_ may incorrectly raise NoSuchProcess_ instead of ZombieProcess_.
• [macOS]: double free() in Process.environ()_ when it fails internally. This posed a risk of segfault.
• [macOS]: massive C code cleanup to guard against possible segfaults which were (not so) sporadically spotted on CI.

Compatibility notes

• stop publishing prebuilt Linux and Windows wheels for 32-bit Python.

[pierre]

Fr running tests with the instructions in the book, you need in addition to rm psutil/init.py: this allows testing the installed module.

Furthermore, with python-3.14, the tests hang. Fix at ​https://github.com/giampaolo/psutil/pull/2666. Can be made into a sed:

sed "/multiprocessing.Pool/i\            multiprocessing.set_start_method('fork')" \
    -i psutil/tests/test_process_all.py

(hope I have the right number of spaces)

[Bruce Dubbs]

I did that but still got 26 failures. See #22244

[pierre]

Replying to Bruce Dubbs:

I did that but still got 26 failures. See #22244

Yes, I have the same errors with the instructions in the book... Looks like the "scripts" module is missing! Let me add it in venv.

[pierre]

Replying to pierre:

Replying to Bruce Dubbs:

I did that but still got 26 failures. See #22244

Yes, I have the same errors with the instructions in the book... Looks like the "scripts" module is missing! Let me add it in venv.

No, I'm wrong. I think there is a mixture of tests in the installed package and tests in the local package... The right thing to do is copy the libraries:

cp build/lib*/psutil/*.so psutil

I then have only two failures...

[Bruce Dubbs]

I'm in favor of leaving it as "This package does not have a working test suite." but if you want to change it, please go ahead.

[pierre]

Replying to Bruce Dubbs:

I'm in favor of leaving it as "This package does not have a working test suite." but if you want to change it, please go ahead.

It is much simpler to run the tests by activating the virtual env and just running "make test". But it seems activating a virtual env may mess up non bash shells...

[Bruce Dubbs]

Fixed again at commit 869e7d0bc0.

[pierre]

Test fixed at 56f0306cb9

[Bruce Dubbs]

Milestone renamed