Removed upper bound on Python version #252
Merged
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.
This is unnecessary (Python is not SemVer'ed) and breaks dependency solvers.
See https://github.com/orgs/python-poetry/discussions/3757#discussioncomment-435337 which describes someone hitting the same problem with a different package and nedbat/coveragepy#1020 for another example.
See also https://twitter.com/codewithanthony/status/1362181541191766017
To be concrete I'm trying to set a correct bound of
python = ">=3.8.0"
in my pyproject.toml, but I get this error from poetry, caused by the upper bound in WebTest:The authors of poetry will not change this behaviour: python-poetry/poetry#5709