-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the simplest 'poetry install' fails #5490
Comments
@mr-xeroth looks to me for some reason, Poetry thinks the active project environment is the system environment. Can you provide the following?
|
here's my docker log. no issues, gotta dig my stuff on my own.
|
@abn So I dug through the docker:
my system:
|
I encountered the same issue, and I think some mix of the following fixed it:
I believe this is a distro packaging bug (Fedora bug report). In my case, Fedora 36, changed the way it tried to install packages to The related Python bug mentions Ubuntu, so they might have encountered a similar problem. If so, it worked in Docker because there was no virtualenv py_info cache there. |
@refi64 I've installed |
@mr-xeroth in your case it looks like Poetry executes your system python instead of the venv python. As for @refi64 's comment you might want to make sure you are upgrading virtualenv in your Poetry environment and not just your systen environment. Something like this: $ cat $(which poetry) | head -n 1
#!/home/abn/.local/pipx/venvs/poetry/bin/python
$ /home/abn/.local/pipx/venvs/poetry/bin/python -m pip install --upgrade virtualenv |
@refi64 I've been racking my brain all morning on this... clearing the cache saved me. Thanks for that! |
Facing the same issue, if I create a
where as if I create a new
output of my
Basically sys.path as |
I was having a lot of problems and some error messages like the ones reported here. I saw pypa/setuptools#3278 and the workaround was setting the env var |
This helped me. Thanks |
Closing this for now as this is related to distro/setuptools bugs that are either resolved or documented (e.g. on the installer repo). |
I ran into the same problem. Work-a-round is to create the venv first, e.g.:
Then poetry used the existing .venv and the bug pypa/setuptools#3278 didn't happen. |
This is documented/well known as #6371; |
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. |
Working environment is Python 3.10.4 on Ubuntu 22.04 LTS
The text was updated successfully, but these errors were encountered: