On 2/5/25 02:47, Miro Hrončok via python-devel wrote:
Hello Pythonistas.
When we updated tox from version 3 to 4, it no longer fails when here is no suitable tox configuration found. This was a deliberate upstream choice.
Unfortunately, it means that packages that use %pyproject_buildrequires with -t or -e now silently succeed if there is no tox configuration found.
I identified 95 packages that are affected by this, see below.
Unfortunately, it is tricky to detect a missing tox configuration directly from %pyproject_buildrequires. For now, I did this by looking for a specific information in tox output, but that might not be stable.
I built all Rawhide packages matching %{?pyproject_buildrequires\s+(.+ \s)?-\S*[te] in a copr with a modified version of %pyproject_buildrequires which fails when this happens.
https://copr.fedorainfracloud.org/coprs/churchyard/pyproject- buildrequires-no-tox-error/builds/
For all the failures, I looked into the logs and identified the 95 failures are caused by that (see below).
If this affects your package, please consider if your usage of -t/-e for %pyproject_buildrequires is a mistake (and remove it), or see if some explicit build dependencies are missing (and the package only builds by chance).
Sometimes, upstreams which use tox don't put their tox configuration into sdist (%pypi_source) and only keep it in git.
Sometimes, upstreams don't use tox at all and the usage of -t/-e is wrong.
If you have questions, I am happy to help.
Maintainers by package:
python-archspec orion python-envisage orion
Fixed. Thanks - the -t was likely just blindly copied before I understood what it meant.
python-pymongo apevec cstratak hhorak jonathanspw orion
https://src.fedoraproject.org/rpms/python-pymongo/pull-request/9