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
I am on the latest stable Poetry version, installed using a recommended method.
I have searched the issues of this repo and believe that this is not a duplicate.
I have consulted the FAQ and blog for any relevant entries or release notes.
If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.
Issue
When installing Poetry from the curl'able script, it conflates "already have requested version" and "already have latest version", which is misleading. An example terminal session:
$ curl -sSL https://install.python-poetry.org | python3.9 - --version 1.5.0
[ snip ]
Installing Poetry (1.5.0): Done
Poetry (1.5.0) is installed now. Great!
You can test that everything is set up by executing:
`poetry --version`
$ curl -sSL https://install.python-poetry.org | python3.9 - --version 1.5.0
Retrieving Poetry metadata
The latest version (1.5.0) is already installed.
$ curl -sSL https://install.python-poetry.org | python3.9 -
[ snip ]
Installing Poetry (1.5.1): Done
Poetry (1.5.1) is installed now. Great!
You can test that everything is set up by executing:
`poetry --version`
1.5.1 is latest, but when I reinstall 1.5.0 explicitly, it calls it the "latest version (1.5.0)".
This was briefly misleading as I was fixing some install issues on my project this morning. The issues themselves were resolved by upgrading Poetry, but I didn't realize at first that this was an option because this version pinning was being done by a set-everything-up script and the logging, of course, implied that upgrading Poetry was not a potential solution.
I would suggest splitting the logging into a two branches for clarity:
The requested version (x.y.z) is already installed. The latest version is a.b.c.
The latest version (x.y.z) is already installed.
The text was updated successfully, but these errors were encountered:
seansfkelley
changed the title
Install script prints misleading error message when you already have the version specified by --version
Install script prints misleading message when you already have the version specified by --versionMay 30, 2023
-vvv
option) and have included the output below.Issue
When installing Poetry from the curl'able script, it conflates "already have requested version" and "already have latest version", which is misleading. An example terminal session:
1.5.1 is latest, but when I reinstall 1.5.0 explicitly, it calls it the "latest version (1.5.0)".
This was briefly misleading as I was fixing some install issues on my project this morning. The issues themselves were resolved by upgrading Poetry, but I didn't realize at first that this was an option because this version pinning was being done by a set-everything-up script and the logging, of course, implied that upgrading Poetry was not a potential solution.
I would suggest splitting the logging into a two branches for clarity:
The text was updated successfully, but these errors were encountered: