Skip to content
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

.postX versions in Python projects are incorrectly treated as a lower version #3945

Open
ghost opened this issue Jun 20, 2021 · 1 comment
Open
Labels
L: python:pip Python packages via pip L: python:poetry Python packages via poetry T: bug 🐞 Something isn't working versioning

Comments

@ghost
Copy link

ghost commented Jun 20, 2021

Package ecosystem: poetry / pip
Package manager version: poetry 1.2.0a1, pip 21.1.2
Language version: 3.9.5
Manifest location and content prior to update:

What you expected to see, versus what you actually saw
It should consider aiohttp==3.7.4.post0 as up to date, but it wants me to update the dependency to an older version (3.7.4).
Native package manager behavior
poetry and pip both correctly consider 3.7.4.post0 to be newer than 3.7.4, per https://www.python.org/dev/peps/pep-0440/#post-releases
Images of the diff or a link to the PR, issue or logs

Screenshot

If I actually try creating a security update, however, it says it is "no longer vulnerable":

Screenshot

🕹 Bonus points: Smallest manifest that reproduces the issue
requirements.txt:

aiohttp==3.7.4.post0
@ghost ghost added the T: bug 🐞 Something isn't working label Jun 20, 2021
@asciimike asciimike added L: python:pip Python packages via pip L: python:poetry Python packages via poetry labels Jun 21, 2021
@jeffwidman
Copy link
Member

Possibly caused by:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: python:pip Python packages via pip L: python:poetry Python packages via poetry T: bug 🐞 Something isn't working versioning
Projects
None yet
Development

No branches or pull requests

3 participants