-
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
Poetry 1.1.8 POETRY_VIRTUALENVS_CREATE=false install broken #4414
Comments
I'm guessing thats ubuntu 20.4... I have a similar problem in this weeks release. It seems like poetry is using the system python to install when you do "POETRY_VIRTUALENVS_CREATE=false" instead of the python env you are currently in. for example $(which python3) -m pip install --disable-pip-version-check --quiet virtualenv setuptools wheel
venv/bin/python -m pip install --disable-pip-version-check poetry
venv/bin/poetry config virtualenvs.create false
venv/bin/poetry install --no-dev would (prior the a release on Tuesday?) install the poetry dependancies inside of the newly created venv, but now, it attempts to install them inside the system python ( $(which python3) ) unfortunately! If I "activate" the venv As an alternate using poetry completely (I was initially try to avoid installing poetry globally on my web servers, but guess it works :) ) Using poetry to manage the venv vs virtualenv. The only difference seems to be the name ( curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/install-poetry.py | $(which python3) -
"$HOME/.local/bin/poetry" config --local virtualenvs.create true
"$HOME/.local/bin/poetry" config --local virtualenvs.in-project true
"$HOME/.local/bin/poetry" install --no-dev |
Same here with alpine 3.14. poetry.toml [virtualenvs]
create = false
|
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. |
Got this weird issue for my production docker build.
RUN POETRY_VIRTUALENVS_CREATE=false poetry install
. I am still investigating why, but downgrade 1.1.7 fix this.The text was updated successfully, but these errors were encountered: