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
If pyenv created a .python-version file inside of the current directory through pyenv local X.XX (where X.XX is the version of course), there should be a check in poetry init to read the .python-version file if it exists and if the user did not specify a version (just hit enter or left blank), the creation of the pyproject.toml will set the python version under [tool.poetry.dependencies] to the version set in that file. You could also have it show the version loaded from the file as the default version in the interactive questions.
This would be an excellent feature for a future release. :-)
The text was updated successfully, but these errors were encountered:
btegs
changed the title
[Feature Request] "poetry init" to read .python-version to define Python version
[Feature Request] "poetry init" to read .python-version to define Python version if none given
Feb 11, 2020
btegs
changed the title
[Feature Request] "poetry init" to read .python-version to define Python version if none given
[Feature Request] "poetry init" to read .python-version to autodetect default Python version
Feb 11, 2020
At Poetry we try to avoid implementations specific for third-party tools. But maybe it's possible to implement it as a plugin. Or you give #4852 a try. Maybe this works as well :)
If pyenv created a
.python-version
file inside of the current directory throughpyenv local X.XX
(where X.XX is the version of course), there should be a check inpoetry init
to read the.python-version
file if it exists and if the user did not specify a version (just hit enter or left blank), the creation of the pyproject.toml will set the python version under [tool.poetry.dependencies] to the version set in that file. You could also have it show the version loaded from the file as the default version in the interactive questions.This would be an excellent feature for a future release. :-)
The text was updated successfully, but these errors were encountered: