-
Notifications
You must be signed in to change notification settings - Fork 295
python3 incorrect permissions on pip #469
Comments
That's awfully strange. Any idea why |
It appears to have been introduced 2 days ago by this commit (I did a checkout and install on a clean VM) b83eb23 I'm new to this codebase so not sure about the cleanest way to fix it. |
I'm not sure what's gone wrong. I'll leave this issue open in the hopes that someone is able to help troubleshoot. |
May need to ping @tdsmith who is our Python expert. |
Can you elaborate wrt which file you modified and how you demonstrated that it helped? |
I just set everything to be writable (so not a proper solution at all), then reran the end of the install (which then worked):
It occurs on a fresh install of CentOS 6.6 & 7.0, and Ubuntu Trusty. |
We don't want to run ensurepip, which installs an old version of pip; we take care of this ourselves in postinstall. On flat (i.e. non-Framework) builds, ensurepip causes an error in postinstall because the pip-3.4 script already exists in prefix/bin. Will resolve Linuxbrew/legacy-linuxbrew#469.
The python3 build runs ensurepip by default. For Framework builds, the pip script ends up getting written somewhere in the Framework tree, so it doesn't cause a conflict. Linuxbrew does a non-framework build, which exposes the conflict. Homebrew/legacy-homebrew#41544 disables running ensurepip and will resolve this issue the next time Shaun merges from Homebrew/homebrew. |
Thanks for reporting & the detailed reproduction instructions, btw! |
Thanks for the fix, Tim. |
Thanks for getting to the bottom of it so quickly. Andrew |
Conflicts: Library/Formula/dos2unix.rb Library/Formula/python.rb Library/Formula/python3.rb Closes #469
Conflicts: Library/Formula/dos2unix.rb Library/Formula/python.rb Library/Formula/python3.rb Closes Linuxbrew/legacy-linuxbrew#469
When installing python3 it fails at the end. Setting chmodding pip with +w fixes the issue.
To replicate the issue on a clean CentOS7 VM with vagrant & virutalbox:
The text was updated successfully, but these errors were encountered: