On 04. 11. 21 12:49, Miro Hrončok wrote:
Hello Pythonistas.
After some recent improvements in the Python RPM dependency generators,
a regression was discovered [0].
Turns out the error happened when the upstream metadata contained a
requirement with a PEP 440 [1] incompatible version. A fix is pending
and only one package in Fedora was affected.
[...]
tl;dr:
- there might be cases where legacy versions are needed
- but in most cases, they should be avoided
Hence, I propose we do the following in Rawhide:
We turn LegacyVersions to failures, but we provide a stop-gap measure,
such as (%global python_dependency_allow_legacy_version_provides 1 /
%global python_dependency_allow_legacy_version_requires 1 ) for packages
that need to override this. When pypa/packaging actually drops
LegacyVersion, this stop-gap measure will no longer work.
I suggest removing LegacyVersion support without replacement. I think
neither creating nor using
"python_dependency_allow_legacy_version_requires" would be worth the
extra work.
All the uses of it that we've seen were mistakes, and since upstream
tools are removing support for it, the stop-gap is just delaying the
inevitable.
If we find an actual use case for it, it can always be added.
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
