-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PEP 440: Note case where pkg_resources subsequently changed to match the PEP #881
Comments
Using bisect, I found the relevant commit is pypa/setuptools@9382fa0.
|
So Setuptools 6.0 was the version. |
Thanks! |
@ncoghlan is there any action to be taken here? I'll close the issue if not. A |
If there's an update needed, perhaps it should be on the PyPA specifications page instead |
This only affects the part of the PEP that compares it to the way pkg_resource.parse_version used to work, so there isn't any impact on the spec itself, just on the background info. I posted a PR to add a note about it, which will close this issue when merged. |
According to https://mail.python.org/archives/list/[email protected]/message/OXN53BWJYSMFK535OWUJR5MAXEIBWRBX/, some time since https://www.python.org/dev/peps/pep-0440/#summary-of-differences-from-pkg-resources-parse-version was written,
pkg_resource.parse_version
started ordering local version numbers the same way that PEP 440 does.@jaraco Do you have any idea when that might have changed? https://setuptools.readthedocs.io/en/latest/history.html doesn't call it out explicitly anywhere, so I'm wondering if it might have happened inadvertently while converging on a shared supported library.
The text was updated successfully, but these errors were encountered: