Fedora Account System
Red Hat Associate
Red Hat Customer
python-time-machine fails to build with Python 3.15.0a3. _______________________________ test_date_today ________________________________ def test_date_today(): with time_machine.travel(EPOCH): today = dt.date.today() > assert today.year == 1970 E assert 2025 == 1970 E + where 2025 = datetime.date(2025, 12, 19).year https://docs.python.org/3.15/whatsnew/3.15.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.15/fedora-rawhide-x86_64/09935440-python-time-machine/ For all our attempts to build python-time-machine with Python 3.15, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.15/package/python-time-machine/ 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.15: https://copr.fedorainfracloud.org/coprs/g/python/python3.15/ Let us know here if you have any questions. Python 3.15 is planned to be included in Fedora 45. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.15. 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.
It looks like this change in Python could be the culprit: https://github.com/python/cpython/commit/fc3e22a06c9b7c93ee379b5554a40a275745e15f
Updating to the latest released version (3.2.0) does not solve this.
Also reproducible from upstream git main. Reported as https://github.com/adamchainz/time-machine/issues/610
https://src.fedoraproject.org/rpms/python-time-machine/pull-request/7