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
Installing ipython on MacOS X tries to install to /System #426
Comments
pip install --user ipython does work |
ipython uses the Regardless, it appears to me that what you're seeing is a straight-up permissions failure which likely would have caused the installation to fail anyway, even in the absence of these
Thanks for the report, but I don't see any bug in pip here, closing. |
Well users (and developers) are strongly encouraged to not write to /System/Library, Apple effectively "owns" that directory and any system update can and probably will stomp all over any user added files. You're quite correct sys.prefix is pointing there:
However the actual packages installed by pip go into /Library (in my case /Library/Python/2.7/site-packages) just fine (which the user is in control of and shouldn't be overwritten in system update). I'm not sure why packages go into /Library and package data into /System/Library Obviously something is in conflict here and I'm not enough of a python distutils expert to know what. However I do know that easy_install does seem to do the right thing. What this does mean is that users with the OS built-in python are unable to install ipython (and other packages that use the same feature) without a sudo. And if they do use sudo they're installing parts of the ipython to a directory that can and will get overridden by an OS system update. |
I think this issue should be reopened (it was closed while I was writing my follow up comment). While yes, technically pip is just doing what it thinks it should be doing, it is trying (although failing due to permissions) This potentially affects anyone who is trying to use pip with the system installed version of python (will like to test hand installed pythons too). |
What's in conflict here, as I said before, is distutils assumptions around The reason This is something that will only be fixed by either Apple fixing the layout of framework builds to match more closely how it works on other platforms, or distutils changing the documented behavior of |
Alright. Fair enough. Not your bug, even if it rather dramatically limits the usefulness of pip. I'll see where I can file this bug next… |
If you want to see this bug without involving pip at all, try running a regular (My recommendation, FWIW, is for ipython and all other packages to simply avoid the use of |
The workaround (at least for ipython) is to add these lines to ~/.pydistutils.cfg:
|
So, basically, this bug is in the cpython tree? |
@SamB Well, it's a bad interaction between a not-very-sophisticated feature in distutils ( The most likely path to getting the bug fixed in a reasonable time frame would actually be for ipython's |
Trying to install ipython "out of the box" on Mac OS X 10.7 using pip fails
It looks like it's trying to install files into "/System/Library/Frameworks/Python.framework/Versions/2.7/share"
There's no reason anything should be installed in there by pip.
Related? #295 and ipython/ipython#1231 (comment)
The text was updated successfully, but these errors were encountered: