The Apple version of Python adds several directories under /System/Library/Frameworks/amework/Versions/2.7/ to the python search path above the standard user-accessible package installation locations.
That message is also OSError:, but it comes after a message like Uninstalling six-1.4.1. But now pip will crash with an error message while trying to remove the old package. This was also a bad idea, and is no longer possible with SIP. On previous versions of OS X, when you installed a package that needed a newer version of one of these, sudo pip would silently remove the old version from the /System/ folder and install a newer version in /Library/Python/2.7/site-packages.
It gives messages like OSError: Operation not permitted: '/System/Library/Frameworks/amework/Versions/2.7/share'Īpple installs outdated versions of some packages in /System/Library/Frameworks/amework/Versions/2.7/Extras/lib/python/ (e.g., six). However it fails on El Capitan due to SIP. This is a bad idea, but in earlier versions of OS X, it succeeded if pip was run with sudo. SIP on El Capitan exposes three problems with using pip with the Apple-supplied version of Python on OS X:ĭistutils does not set two important variables correctly on Macs, so pip tries to write headers and other shared files (e.g., manpages) under /System/Library/Frameworks/amework/Versions/2.7/. However, System Integrity Protection (SIP) on El Capitan blocks several bad practices with pip that used to slide by, so you will probably need to make some more changes to get pip running smoothly on El Capitan. The quick fix is to use a pip command like this: sudo -H pip install -install-option '-install-data=/usr/local' This problem often arises when pip tries to install a manpage for IPython on El Capitan.
0 kommentar(er)
