Replies: 2 comments 5 replies
-
@mbrancato looks like you have poetry installed in the same environment that you are managing. This is bad. And in any case, and Poetry does not use the pip or packaging from within the project's virtual env (#2826). |
Beta Was this translation helpful? Give feedback.
4 replies
-
@mbrancato #10091 should resolve the issue you are facing. Would be good if you can test it out. Can you please try the fix at #PULL_ID. Using pipxpipx install --suffix=@10091 'poetry @ git+https://github.com/python-poetry/poetry.git@refs/pull/10091/head'
alias poetry=poetry@10091
poetry install Using a container (podman | docker)podman run --rm -i --entrypoint bash python:latest <<EOF
set -xe
python -m pip install --disable-pip-version-check -q git+https://github.com/python-poetry/poetry.git@refs/pull/10091/head
...
poetry install
EOF |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've noticed several issues which are related to
EnvCommandError
orCalledProcessError
. Many of these seem to be an issue that I have experienced and can reproduce related to a race condition with core packages. When packages likesetuptools
,wheel
, orpip
are included in the lock file, commands likepoetry update
andpoetry install
can fail when performing installations. The process seems to be related to parallel install workers. When, for example, the packagepip
is being updated, other workers callingpip
will fail.This can be resolved by setting
POETRY_INSTALLER_MAX_WORKERS=1
on the env. Part of the issue here is that the packages do not explicitly call out a dependency onpip
or others, and whenpoetry
builds a graph for ordering installation, it is not taking into account its own use ofpip
and others to install the packages.Example:
With only 1 worker, this does not happen:
Beta Was this translation helpful? Give feedback.
All reactions