Created attachment 1943858 [details]
simple naive patch

python-psutil fails to build with Python 3.12.0a5.

This seems like some precision error. With rounding to two digits the tests pass.

======================================================================
FAIL: psutil.tests.test_system.TestCpuAPIs.test_cpu_times
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/psutil-release-5.9.2/psutil/tests/test_system.py", line 349, in test_cpu_times
    self.assertEqual(total, sum(times))
AssertionError: 579.5100000000001 != 579.51

======================================================================
FAIL: psutil.tests.test_system.TestCpuAPIs.test_per_cpu_times
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/psutil-release-5.9.2/psutil/tests/test_system.py", line 388, in test_per_cpu_times
    self.assertEqual(total, sum(times))
AssertionError: 289.59 != 289.59000000000003

----------------------------------------------------------------------
Ran 557 tests in 2.426s

https://docs.python.org/3.12/whatsnew/3.12.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05513110-python-psutil/

For all our attempts to build python-psutil with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/python-psutil/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.12:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/

Let us know here if you have any questions.

Python 3.12 is planned to be included in Fedora 39. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.12.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.