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

Upper bound on requires-python in pyproject.toml #620

Closed
mbyrnepr2 opened this issue Mar 18, 2024 · 0 comments · Fixed by #621
Closed

Upper bound on requires-python in pyproject.toml #620

mbyrnepr2 opened this issue Mar 18, 2024 · 0 comments · Fixed by #621
Labels
bug Something isn't working

Comments

@mbyrnepr2
Copy link
Contributor

Describe the bug

Hi folks!

There is a note at the end of the page writing-pyproject-toml which links to a blog bound-version-constraints. In this blog there is a section entitled pinning the Python version is special and mentions some considerations when putting an upper bound on a project's Python version, e.g:
if someone adds a cap or tightens a cap, unless they yank every single older release, a locking solver like Poetry or PDM will backsolve to the last versions without the cap so that the lock file it creates will be “valid” on all the Python versions you are requesting!

Perhaps it is good to consider this upper bound and instead specify a lower bound only, in case there are issues later on.

Thanks for your time!

Additional context
Python Discourse discussion

@mbyrnepr2 mbyrnepr2 added the bug Something isn't working label Mar 18, 2024
@mbyrnepr2 mbyrnepr2 changed the title Bug Summary Upper bound on requires-python in pyproject.toml Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant