Bump psutil from 5.9.8 to 6.0.0

[dependabot]

Bumps psutil from 5.9.8 to 6.0.0.

Changelog

Sourced from psutil's changelog.

6.0.0 2024-06-18

Enhancements

• 2109_: maxfile and maxpath fields were removed from the namedtuple returned by disk_partitions()_. Reason: on network filesystems (NFS) this can potentially take a very long time to complete.
• 2366_, [Windows]: log debug message when using slower process APIs.
• 2375_, [macOS]: provide arm64 wheels. (patch by Matthieu Darbois)
• 2396_: process_iter()_ no longer pre-emptively checks whether PIDs have been reused. This makes process_iter()_ around 20x times faster.
• 2396_: a new psutil.process_iter.cache_clear() API can be used the clear process_iter()_ internal cache.
• 2401_, Support building with free-threaded CPython 3.13.
• 2407_: Process.connections()_ was renamed to Process.net_connections()_. The old name is still available, but it's deprecated (triggers a DeprecationWarning) and will be removed in the future.
• 2425_: [Linux]: provide aarch64 wheels. (patch by Matthieu Darbois / Ben Raz)

Bug fixes

• 2250_, [NetBSD]: Process.cmdline()_ sometimes fail with EBUSY. It usually happens for long cmdlines with lots of arguments. In this case retry getting the cmdline for up to 50 times, and return an empty list as last resort.
• 2254_, [Linux]: offline cpus raise NotImplementedError in cpu_freq() (patch by Shade Gladden)
• 2272_: Add pickle support to psutil Exceptions.
• 2359_, [Windows], [CRITICAL]: pid_exists()_ disagrees with Process_ on whether a pid exists when ERROR_ACCESS_DENIED.
• 2360_, [macOS]: can't compile on macOS < 10.13. (patch by Ryan Schmidt)
• 2362_, [macOS]: can't compile on macOS 10.11. (patch by Ryan Schmidt)
• 2365_, [macOS]: can't compile on macOS < 10.9. (patch by Ryan Schmidt)
• 2395_, [OpenBSD]: pid_exists()_ erroneously return True if the argument is a thread ID (TID) instead of a PID (process ID).
• 2412_, [macOS]: can't compile on macOS 10.4 PowerPC due to missing MNT_ constants.

Porting notes

Version 6.0.0 introduces some changes which affect backward compatibility:

• 2109_: the namedtuple returned by disk_partitions()_' no longer has maxfile and maxpath fields.
• 2396_: process_iter()_ no longer pre-emptively checks whether PIDs have been reused. If you want to check for PID reusage you are supposed to use Process.is_running()_ against the yielded Process_ instances. That will also automatically remove reused PIDs from process_iter()_ internal cache.
• 2407_: Process.connections()_ was renamed to Process.net_connections()_. The old name is still available, but it's deprecated (triggers a

... (truncated)

Commits

• 3d5522a release
• 5b30ef4 Add aarch64 manylinux wheels (#2425)
• 1d092e7 test subprocesses: sleep() with an interval of 0.1 to make the test process m...
• 5f80c12 Fix #2412, [macOS]: can't compile on macOS 10.4 PowerPC due to missing MNT_...
• 89b6096 process_iter(): use another global var to keep track of reused PIDs
• 9421bf8 openbsd: skip test if cmdline() returns [] due to EBUSY
• 4b1a054 Fix #2250 / NetBSD / cmdline: retry on EBUSY. (#2421)
• 20be5ae ruff: enable and fix 'unused variable' rule
• 5530985 chore(ci): update actions (#2417)
• 1c7cb0a Don't build with limited API for 3.13 free-threaded build (#2402)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.