-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Making a virtualenv in the project root fails if <cache-dir>/virtualenvs does not exist #1573
Comments
I have similar problem when cloning project with
|
Maybe we can skip writing the envs file in lib/poetry/utils/env.py:-
|
Ok, so one workaround is to create the "global" virtualenvs dir first:-
|
Seeing this in a dev container, on version
Strangely, when this runs in the Dockerfile that installs poetry it doesn't error, its just follow-up runs. Here's the install.
The workaround presented, I wonder if something is stomping on the cache directory edit: I'm pretty sure the issue is that Github Codespaces is stomping on the cache directory |
This issue also occurs on Read The Docs. I'm fairly certain it's an issue with |
Seeing the same in GitLab CI with both virtualenvs.create=false and POETRY_HOME/POETRY_CACHE_DIR set. Interestingly, it seems to work fine with the same setup in Docker and POETRY_CACHE="/var/cache/poetry". |
The issue arose because I was using: |
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. |
-vvv
option).Issue
It appears that if
poetry
has never made a virtualenv for you—which means that<cache-dir>/virtualenvs
does not exist, then askingpoetry
to make a virtualenv in the project root will fail.I can get past this by either having first made a not-in-project-root virtualenv with
poetry
or by creating the<cache-dir>/virtualenvs
directory manually myself.The text was updated successfully, but these errors were encountered: