Fix handling of dependency markers with python precision >= 3 #2526
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sdispater
added
kind/bug
This was referenced Jun 9, 2020
Merged
3 tasks
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a dependency was specifying a
pythoncondition with a python version with a precision of 3 or more (for instance,>=3.5,<3.5.4), it would generate an incorrect marker leading to issues while evaluating the marker against the environment.For instance, the
>=3.5,<3.5.4condition would generate the following marker:python_version >= "3.5" and python_version < "3.5.4". However, the correct marker is:python_version >= "3.5" and python_full_version < "3.5.4".Pull Request Check List