-
Notifications
You must be signed in to change notification settings - Fork 3.1k
lib path is hardcoded in backwardcompat/__init__.py:home_lib() #899
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
Comments
in all of the cpython's, the home scheme literally does just use the this is arch linux? we do have a |
slackware64 current |
let me work up a pull tomorrow, and you can try it. |
merged the pull request for this. |
I can still reproduce this using:
on
But the lib64 variant is present:
|
is the lib path in |
Sorry, I wasn't sure where to post this. At first I thought it might be a regression (and it still may be), |
library path in home_lib() in backwardcompat/init.py is hardcoded to 'lib' this breaks when the system default is lib64.
pip install --target /home/user/twitter-pip twitter
displays the problem.
the directroy created during install is
/tmp/tmpXgpY70/lib64/
i don't have a good fix but i did check for the 'ARCH' environmental variable and set the lib directory accordingly in the home_lib() function.
The text was updated successfully, but these errors were encountered: