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
This comment by Charlie I think summarizes the situation well:
The .python-version file is not quite obsolete with requires-python -- they're subtly different. requires-python is the range of versions supported by your project. .python-version is the exact version you want to use when developing. For example, if you're working on a library, your requires-python might be >= "3.10". But when developing on your machine, you might want to use 3.12.4 by default -- so you'd set that in a .python-version.
Since these two values are different, and pyproject one should ideally be looser, I think this continues to be something we don't plan to change.
Question
Wouldn't it be cleaner to include the python version to use in the
pyproject.toml
file, instead of creating a separate.python-version
file?Platform
No response
Version
No response
The text was updated successfully, but these errors were encountered: