-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
Possible feature: Support .python-version #1126
Comments
Thank you for expanding on how the resolution would work! I am open to this 🙂 |
Somewhat unrelated, but would this functionality be useful to you? #1124 (comment) |
Let’s ask people if they want this. It was just an idea that I had to ease transition. I’m personally committed to Hatch lol
answered there |
since the proposed feature adapts one of the many non-standard practices in the ecosystem, i propose to implement this in an Environment Collector plugin. |
+1 My use case is that I have an application project which requires everyone on the team to be on the same Python version as the one deployed in production. However, my team has not adopted Hatch. Having
|
pyenv and Rye both use a .python-version file to define what version they use.
Pros
Hatch could use it as a default for
hatch.envs.default.python
, and itCons
Impact
It would make the fallback chain for the Python version look something like the following
hatch.envs.<env>.overrides.<matching condition>.python
hatch.envs.<env>.python
hatch.envs.default.python
(assuminghatch.envs.<env>.template = 'default'
or unspecified)project.requires_python
The text was updated successfully, but these errors were encountered: