This is a tracking bug for Change: Setuptools 74+ For more details, see: https://fedoraproject.org/wiki/Changes/Setuptools_74%2B Update to a new upstream release of python-setuptools that is not completely compatible with previous releases. Most notably, version 72.0.0 removed support for the setup.py test command (deprecated for 5 years). This is a breaking change and Fedora packages that use the setup.py test command during the build need to be adapted to use a different test runner, such as unittest, pytest, etc. There might be other breaking changes. We estimate 142 to 196 Fedora Rawhide packages to fail to build due to this upgrade (as of Sep 2024). If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Thanks for the heads up! I've locally enabled the test calling pytest directly but then they fail. But I realize in previous versions there was no test running: ``` writing manifest file 'jinja2_time.egg-info/SOURCES.txt' running build_ext ---------------------------------------------------------------------- Ran 0 tests in 0.000s ``` And indeed running them manually on my current FC40 also leads to failure. Does it sound reasonable to you if I just disable them for the time being (so would be de-facto equivalent to previous releses)? I'm actually considering as well if it is worth fixing or orphaning the package, as I maintained it since it was a dependency for python-cookiecutter but that doesn't depend on jinja2-time anymore (they have just inlined the code here inside instead of using the separate module, I guess since it was unmaintained upstream from a long time) so now keeping this one may be not worth. Thanks for your input! F.
(In reply to fedepell from comment #1) > Thanks for the heads up! Sorry this went to the wrong bugzilla ticket :-/ Is there a way to delete? I cannot seem to find one :-(
> Is there a way to delete? No, but never mind.