Choose the host Python version used when running poetry installed with 'get-poetry.py'

Follow up to this issue:

• How to disable Poetry 1.1 warnings? (#3029)

Since #2683 a EOL warning message is displayed when poetry runs under a Python interpreter that has reached its end of life (EOL), for example Python 2.7, and 3.5. Fair enough. But when using a poetry installation initiated with get-poetry.py it does not seem possible to control which Python interpreter is being used. Which leads to the EOL warning message being legitimately displayed but there is no straightforward way for the user to switch to a different Python version. It is not reasonable to expect from the users that they uninstall the older Python interpreters.

Related

• How to disable Poetry 1.1 warnings? (#3029)
• No method to control the python version used (#522)
• poetry default to using python instead of python3 (#3184)

[sontek]

@sinoroc Yeah, I’m more of discussing this because the ergonomics around it don’t make sense to me and I would like to start recommending people use Poetry over things like pip and pipenv. So even though I know how to work around this flaw, I don’t believe its safe to recommend use of the software when it’ll be something MAJORITY of users hit.

Most systems aren’t defaulting to python3 for “python” and having to work around it is a weird limitation with many easy fixes.

[finswimmer]

The get-poetry.py script is now deprecated in favor of install-poetry.py, which will bind poetry to the python version it was installed with. See https://python-poetry.org/blog/announcing-poetry-1.2.0a1/#deprecation-of-the-get-poetrypy-script

As a downside the “pyenv workflow” no longer works.