"This installer is deprecated" with recommended install
See original GitHub issue-
I am on the latest Poetry version.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option). -
OS version and name: Docker image
python:3.9.5-buster
-
Poetry version: Installing from
master
-
Link of a Gist with the contents of your pyproject.toml file: Not relevant
Issue
When installing Poetry according to the documentation by running
curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python -
The following warnings is printed:
This installer is deprecated. Poetry versions installed using this script will not be able to use ‘self update’ command to upgrade to 1.2.0a1 or later.
This seems to be because of c28728fbe3e69c9995a4ea132dd767074f00e6f8. I think the root of the issue is that the instructions recommend you use master
to install the current version (1.1), but master
has already been updated to the 1.2 situation with the deprecation.
I think either the recommended install should use the 1.1
branch, or master
should be reverted not to issue deprecation warnings until 1.2
is released.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:12
- Comments:5 (1 by maintainers)
Thank you for your response and your work on Poetry.
I understand that
get-poetry.py
install the version from releases, but the code ofget-poetry.py
itself does depend on the branch, and it’s currently issuing a warning that is not yet relevant until 1.2 is released.I just think it’s a bad user experience to follow the official instructions and get a deprecation warning, even though there’s nothing you can do about it. If this is the intent, maybe the wording should be changed to still warn the user that 1.2 will require a reinstall, without sending them searching for the non-deprecated installer which isn’t released yet.
Thanks again!
I know this issue is closed but I think @nzig brings up a very valid and important point. I’m relatively positive that I’m not the only person who clicked the little thumbs up on his comment because we wound up here googling “Okay, so how am I supposed to install poetry if the script from the documentation is the wrong way to do this”
I think perhaps the wording should be changed from saying “This script is deprecated” to something like