-
Notifications
You must be signed in to change notification settings - Fork 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
pip install --target fails #3056
Comments
I have independently ran into this issue while trying to install lxml. It gives a similar trace as this other issue. Here is the Dockerfile I created to reproduce the issue.
|
see #3450 |
-- fix using pip with --target option (pypa/pip#3056 and pypa/pip#3450)
Any pointers for working around this issue? |
Shouldn't this be fixed in pip 8.1.2? See #3694 |
@wm75 Aha, yes! Upgrading from pip 8.1.1 to 8.1.2 has fixed this issue. Thanks. |
The Dockerfile I submitted still reproduces the problem, even though it is using the latest pip (8.1.2). |
@movermeyer We are using CentOS 7 and upgrading to 8.1.2 resolved the issue for us. |
I reproduce the issue on Amazon Linux Docker Container. Dockerfile is very very simple. FROM 137112412989.dkr.ecr.ap-northeast-1.amazonaws.com/amazonlinux:latest
RUN curl -sL https://bootstrap.pypa.io/get-pip.py | python
RUN pip install lxml -t libs Then,
There is '/tmp/tmpld2WbC/lib64/python'. Any workaroud? |
I'm also experiencing this issue on Fedora 25 with the
Allowing
|
Hey! It seems like it's been a while since this issue was active. I've spent some time fiddling with this option so, it might be that this has been fixed along the line. Could someone try reproducing this issue on the current master? Thanks and sorry for the wait. |
I'm no longer hitting this issue with Pip 9.0.1 on Fedora 27:
|
Great! A second confirmation and I'll be happy to close. |
Well, one confirmation and a lack of activity should be enough reason to close. :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Full Log: https://gist.github.com/chrismeyersfsu/6967e1f41db9660cdc1b
Also ran
pip install pip --upgrade
(to v 7.1.2) and still had the same error.Dockerfile
Also tried
DISTUTILS_DEBUG=1 pip install -t /tmp/me --install-option="--install-purelib=\$base/lib64/python" billiard
Fails and doesn't seem to effect theinstall_purelib
disutils variable.https://gist.github.com/chrismeyersfsu/709a80df91176bc9f7bc
Solution:
Creating a
setup.cfg
with below contents successfully effected the disutilsinstall_purelib
variable.DISTUTILS_DEBUG=1 pip install -t /tmp/install_here -vvvv psutil
Log: https://gist.github.com/chrismeyersfsu/036b494a2a37d636839b
Reflections:
My question now is, who is at 'fault' ? Should pip default to using the
purelib
directory? Or should a directive exist that complements--target
to choose the variable from which to look for the artifacts (i.e. --target-use <purelib, lib>)Further, why did
--install-option="--install-purelib=\$base/lib64/python"
have no effect?The text was updated successfully, but these errors were encountered: