-
-
Notifications
You must be signed in to change notification settings - Fork 612
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-sync fails when run from long paths #546
Comments
The following change would fix the issue when run within virtualenv.
I haven't tried out fixing the absolute path usage but presumably it would be something like:
|
vlovich
changed the title
pip-sync fails unpredictably when run from long paths
pip-sync fails when run from long paths
Jul 26, 2017
ping. |
This was fixed in #737. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When pip-sync detects it's running in a virtual environment it invokes the "pip" executable. However, the shebang line in the pip executable could be too long to acommodate this & the pip command fails in surprising fashion (i.e. it's not an immediate error but it tries to run some of the installations globally instead of inside the virtualenv which fails with permissions errors).
Environment Versions
Ubuntu 14.04.5
$ python -V
2.7.6
$ pip --version
9.0.1
$ pip-compile --version
1.9.0
Steps to replicate
/usr/local/xxxxxx/home/username-here-xxx/jenkins/workspace/projec/presubmit/xxxxxxx/master/xxxxxxxxx/automation/python-env
Expected result
I would expect pip-sync to succeed.
Actual result
It fails trying to install wrapt in global site packages.
Other notes
Unclear why pip-sync doesn't fail with "bad interpreter".
Monkey-patching pip-sync to invoke "python", "-m", "pip" instead of just "pip" fixes the issue.
Here is the requirements.txt
The text was updated successfully, but these errors were encountered: