Pip vendor modules not found when using Poetry 1.2.1

[markusos]

• Poetry version: 1.2.1
• Python version: 3.8.12
• OS version and name: Debian 11.5 "bullseye"
• pyproject.toml: https://github.com/markusos/poetry-bug/blob/main/pyproject.toml

• I am on the latest stable Poetry version, installed using a recommended method.
• I have searched the issues of this repo and believe that this is not a duplicate.
• I have consulted the FAQ and blog for any relevant entries or release notes.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

After upgrading to Poetry 1.2.1 some dependencies now fails to install with different errors errors for pip._vendor libraries. E.g:

• ModuleNotFoundError: No module named 'pip._vendor.packaging.markers'
• ModuleNotFoundError: No module named 'pip._vendor.distlib'
• ModuleNotFoundError: No module named 'pip._vendor.urllib3._version'
• ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: '/home/dev/.cache/pypoetry/virtualenvs/[poetry-bug]-p3hG42m9-py3.8/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py'

See full build log here: https://github.com/markusos/poetry-bug/blob/main/build.log

To reproduce check out the https://github.com/markusos/poetry-bug repo and run ./build.sh. This will build a docker container with Poetry 1.2.1 and use poetry to install this pyproject.toml: https://github.com/markusos/poetry-bug/blob/main/pyproject.toml

The same pyproject.toml and poetry.lock builds fine in the same docker setup if https://github.com/markusos/poetry-bug/blob/main/Dockerfile#L15 is changed to: RUN curl -sSL https://install.python-poetry.org | python3 - --version 1.2.0
to run this with the previous release of Poetry. See build log for Poetry 1.2.0 here: https://github.com/markusos/poetry-bug/blob/main/build_1_2_0.log

This seems like a regression bug in Poetry 1.2.1, but it might be that we're missing something that needs to be migrated in the lock file some new dependency in the setup?

[dimbleby]

duplicate #6567 - pip is in your dependency tree, it's while updating pip that the other parallel installs go wrong.

[neersighted]

Mitigated in #6582 as well, which is currently unreleased in the 1.2 branch.

[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.