You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: