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
{{ message }}
Repository navigation
This "Official Installer Script" fails on Windows #146
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\ScriptsYou 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 environmentInstalling Poetry (1.8.4): Installing PoetryInstalling Poetry (1.8.4): Creating scriptInstalling Poetry (1.8.4): DonePoetry (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:
changed the title [-]This "Official Installer Script" fails on Windows, has become ABANDONWARE[/-][+]This "Official Installer Script" fails on Windows[/+]on Nov 19, 2024
I am quite sure that the installer works fine for lots of people: it is likely that whatever problem you are experiencing is something unusual in your local environment.
Do leave an update if and when you figure it out, perhaps the next person will benefit.
I am quite sure that the installer works fine for lots of people: it is likely that whatever problem you are experiencing is something unusual in your local environment.
And? This is relevant in what way?
Do leave an update if and when you figure it out,
The person asked for help and you dismissed them
... perhaps the next person will benefit.
Well, actually, "I am quite sure that the installer works fine for lots of people," so there will not be a "next person" who needs to benefit from the unusual something that the user will figure out for themselves.
About a week ago, I ran (Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py - from an admin ps
poetry --version produced nothing
I tried using it a few times with things like poetry init but I never got a response or error or anything. for example:
(hhSCNet) C:\apps\hhSCNet>poetry
(hhSCNet) C:\apps\hhSCNet>poetry --help
(hhSCNet) C:\apps\hhSCNet>poetry help
Today, I uninstalled with (Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py - --uninstall and the script said it was uninstalled.
I reinstalled from admin PS. same problem.
Collecting poetry==1.8.5
Using cached poetry-1.8.5-py3-none-any.whl.metadata (6.9 kB)
Collecting build<2.0.0,>=1.0.3 (from poetry==1.8.5)
Using cached build-1.2.2.post1-py3-none-any.whl.metadata (6.5 kB)
Collecting cachecontrol<0.15.0,>=0.14.0 (from cachecontrol[filecache]<0.15.0,>=0.14.0->poetry==1.8.5)
Using cached cachecontrol-0.14.1-py3-none-any.whl.metadata (3.1 kB)
Collecting cleo<3.0.0,>=2.1.0 (from poetry==1.8.5)
Using cached cleo-2.1.0-py3-none-any.whl.metadata (12 kB)
Collecting crashtest<0.5.0,>=0.4.1 (from poetry==1.8.5)
Using cached crashtest-0.4.1-py3-none-any.whl.metadata (1.1 kB)
Collecting dulwich<0.22.0,>=0.21.2 (from poetry==1.8.5)
Using cached dulwich-0.21.7-cp313-cp313t-win_amd64.whl
ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'C:\\users\\hunte\\appdata\\local\\pip\\cache\\wheels\\63\\f9\\68\\6bb6145045043643aaf320f7e02bd693edd8db4a4e21472df8\\dulwich-0.21.7-cp313-cp313t-win_amd64.whl'
Check the permissions.
Traceback:
File "<stdin>", line 937, in main
File "<stdin>", line 574, in run
File "<stdin>", line 596, in install
File "<stdin>", line 699, in install_poetry
File "<stdin>", line 389, in pip
File "<stdin>", line 386, in python
File "<stdin>", line 379, in run
My point in noting that the installer works for lots of people is simply that: it generally isn't true that the installer "fails on windows".
If the script did generally fail, then anyone could reproduce the problem and offer help: whereas if it fails only on the reporter's computer then only the reporter is positioned to do any debugging. (A second report now puts us somewhere in between.)
In an earlier comment I linked to a pipeline succeeding with windows and python 3.13 so the issue is certainly not simply about using python 3.13. I would guess that it's not about that at all; but maybe.
I still have little to offer on this one but encouragement: if you figure out what is going on please do leave an update. Perhaps the next person will benefit.
And then tries to write a log to C:\Users\<username>\AppData\Roaming\, but no such log is ever created
3.13 and 3.12 instead report success, but as I said they don't even create C:\Users\<username>\AppData\Roaming\Python\Scripts
Activity
[-]This "Official Installer Script" fails on Windows, has become ABANDONWARE[/-][+]This "Official Installer Script" fails on Windows[/+]dimbleby commentedon Nov 19, 2024
I am quite sure that the installer works fine for lots of people: it is likely that whatever problem you are experiencing is something unusual in your local environment.
Do leave an update if and when you figure it out, perhaps the next person will benefit.
dimbleby commentedon Nov 20, 2024
eg here it is working fine in CI
hunterhogan commentedon Dec 14, 2024
#146 (comment) by https://github.com/dimbleby
And? This is relevant in what way?
The person asked for help and you dismissed them
Well, actually, "I am quite sure that the installer works fine for lots of people," so there will not be a "next person" who needs to benefit from the unusual something that the user will figure out for themselves.
hunterhogan commentedon Dec 14, 2024
tldr
Using Python v3.13 is the likely nexus of the problem. Modify the command to
Chronological troubleshooting
About a week ago, I ran
(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py -from an admin pspoetry --versionproduced nothingI tried using it a few times with things like
poetry initbut I never got a response or error or anything. for example:Today, I uninstalled with
(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py - --uninstalland the script said it was uninstalled.I reinstalled from admin PS. same problem.
Switched to non-admin PS
poetry-installer-error-afrdjhr4.log:
(Because I was in a venv when I ran the command, it isn't clear that my default was 3.13)
make %LocalAppData%\py.ini
I haven't tried any other command, so maybe it is still broken, but getting a response was major improvement, so I decided to share with y'all.
dimbleby commentedon Dec 14, 2024
My point in noting that the installer works for lots of people is simply that: it generally isn't true that the installer "fails on windows".
If the script did generally fail, then anyone could reproduce the problem and offer help: whereas if it fails only on the reporter's computer then only the reporter is positioned to do any debugging. (A second report now puts us somewhere in between.)
In an earlier comment I linked to a pipeline succeeding with windows and python 3.13 so the issue is certainly not simply about using python 3.13. I would guess that it's not about that at all; but maybe.
I still have little to offer on this one but encouragement: if you figure out what is going on please do leave an update. Perhaps the next person will benefit.
hunterhogan commentedon Dec 15, 2024
The original post can be criticized for many things, but this is not one of them.
A link you might enjoy: prolatio.
Mek101 commentedon Jul 2, 2025
I can echo the issue,
C:\Users\<username>\AppData\Roaming\Python\Scriptsisn't even created3.6 fails with
And then tries to write a log to
C:\Users\<username>\AppData\Roaming\, but no such log is ever created3.13 and 3.12 instead report success, but as I said they don't even create
C:\Users\<username>\AppData\Roaming\Python\ScriptsI'm on windows 11