On 04. 11. 21 13:42, Neal Gompa wrote:
On Thu, Nov 4, 2021 at 7:50 AM Miro Hrončok <mhron...@redhat.com> wrote:
...
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.
This makes sense to me, but would it also make sense to have some
documentation about this case and how to resolve it to PEP 440
compatible versions, too?
I would definitively create a description of this in the guidelines and we
could link the error to it. If we want some distro-agnostic place, we could
create a document in
https://github.com/rpm-software-management/python-rpm-packaging
The description should definitively contain migration advice and some
actionable recommendations. However, there is no deterministic way to resolve a
PEP 440 incompatible version to a PEP 440 compatible version, otherwise we
would just do that.
Consider that PEP 440 incompatible version can be practically anything within a
reasonable character set.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
