-
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
package installation failure #7046
Labels
Comments
sileht
added
kind/bug
Something isn't working as expected
status/triage
This issue needs to be triaged
labels
Nov 16, 2022
if you're right, simplest workaround is to upgrade setuptools before cf #6582 |
2 tasks
sileht
added a commit
to sileht/poetry
that referenced
this issue
Mar 22, 2023
If a package is build from source because no pep517 build system are indicated in pyproject.toml or the file is missing, pep517 will fallback to setuptools and wheel installed within the virtualenv to build it. eg: https://github.com/pypa/pip/blob/22.3.1/src/pip/_vendor/pep517/wrappers.py#L167 https://github.com/pypa/pip/blob/22.3.1/src/pip/_vendor/pep517/wrappers.py#L220 https://github.com/pypa/pip/blob/22.3.1/src/pip/_vendor/pep517/wrappers.py#L273 Fixes python-poetry#7046
Still having this issue, python 3.10, poetry 1.4.2, Github CI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
-vvv
option) and have included the output below.Issue
poetry failed to install packages from time to time with the error below.
I suspect it only occurs with the package is not pep518 compatible and pip requires building a wheel.
I'm not sure if it's directly linked to poetry, or if this is just poetry that triggers a pip/setuptools bug?
One of my guess is, setuptools get updated while another package tries to build a wheel and since all setuptools files are replaced during the process, the links/files inside
/tmp/pip-build-env-k0jhdblz/overlay/
may not exists for a short time.It's not 100% reproductive, but it occurs a lot inside our GitHub workflows.
The text was updated successfully, but these errors were encountered: