This "Official Installer Script" fails on Windows
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the official installer command from the issue on Windows 11 with Python 3.13, then inspect the installer entry point at https://install.python-poetry.org and the generated Poetry executable. Done means the installation produces usable poetry --version output and the documented command or PATH setup works as described.
Written by the indexing model from the issue text.
Description
Installed on an up-to-date vanilla Windows 11 machine with Python 3.13 (symlinks enabled), via the official method recommended right here on the website:
PS C:\Users\me> (Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py -
Retrieving Poetry metadata
# Welcome to Poetry!
This will download and install the latest version of Poetry,
a dependency and package manager for Python.
It will add the `poetry` command to Poetry's bin directory, located at:
C:\Users\alexander.chandel\AppData\Roaming\Python\Scripts
You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.
Installing Poetry (1.8.4)
Installing Poetry (1.8.4): Creating environment
Installing Poetry (1.8.4): Installing Poetry
Installing Poetry (1.8.4): Creating script
Installing Poetry (1.8.4): Done
Poetry (1.8.4) is installed now. Great!
To get started you need Poetry's bin directory (C:\Users\me\AppData\Roaming\Python\Scripts) in your `PATH`
environment variable.
Alternatively, you can call Poetry explicitly with `C:\Users\me\AppData\Roaming\Python\Scripts\poetry`.
You can test that everything is set up by executing:
`poetry --version`
PS C:\Users\me> C:\Users\me\AppData\Roaming\Python\Scripts\poetry --version
PS C:\Users\me>
Ok so the installation failed somehow. Calling it explicitly outputs nothing. And it did not bother to add that dir to my USER PATH for me, so it isn't really an "install". Let's add it to the PATH and try again:
PS C:\Users\me> poetry --version
PS C:\Users\me> poetry -h
PS C:\Users\me> poetry -foobar
PS C:\Users\me>
No output at all, literally nothing.
Let's try the absolute path, just in case:
PS C:\Users\me> C:\Users\me\AppData\Roaming\pypoetry\venv\Scripts\poetry.exe --version
PS C:\Users\me> C:\Users\me\AppData\Roaming\pypoetry\venv\Scripts\poetry.exe -h
PS C:\Users\me>
Still nothing. What's going on?
- Dominant language
- Python
- Stars
- 255
- Forks
- 65
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python-poetry/install.python-poetry.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
python-poetry/install.python-poetry.org#144 · 8 comments · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
python-poetry/install.python-poetry.org#177 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in python-poetry/install.python-poetry.org
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·