Question or issue on macOS:

Python for Mac OS X. Pip tool to simplify installing and managing additional packages. Pip is included with Python 3.4 releases; for earlier releases, follow the pip install instructions. Among the packages available through PyPI are some that are specifically for OS X environments. Setuptools + Pip ¶ The two most crucial third-party Python packages are setuptools and pip, which let you download, install and uninstall any compliant Python software product with a single command. It also enables you to add this network installation capability to your own Python software with very little work.

Made the upgrade to Mac OS X 10.8 (Mountain Lion) and get now the following error when trying to call $ pip:

Update: Tried to reinstall by doing the install procedure again (with http://www.pip-installer.org/en/latest/installing.html#using-the-installer and easy_install), but didn’t work, got the same error.

Tried now the following: Calling $ sudo pip and the above error disappears. Strange is, that the directories which could not befound in the above error message point to /System/Library/… while the python installation is (new ?) to find in /Library/Frameworks/.:

Any idea how to get rid of the sudo?

How to solve this problem?

Solution no. 1:

Use easy_install to update your pip to the latest version:

sudo easy_install -U pip

Also make sure you have the lastest XCode installed (ver 4.4) with Command Line Tools.

Solution no. 2:

This works for me

Solution no. 3:

I had a similar error except that sudo pip did not work either. I am using a “brew” installation of python (which is symlinked to /usr/local/bin) and found that the problem was that the shebangs in the pip and easy_install files were hardcoded to #!/usr/bin/python instead of #!/usr/local/bin/python, and so was using the system python version instead of the brew version.

Cheers,
Tom

Solution no. 4:

I actually couldn’t do what was suggested. I instead had to execute:

Then I was able to install the ldap module.

Solution no. 5:

I tried all the answers here, from reinstall easy_install to install a new python version, nothing worked for me. Eko ranger guitar serial numbers.

What I did was install a fresh Python install in the /Library/Frameworks folder, and symlink to that one from /usr/local/bin (for some reason, my system had a symlink from /Library/Frameworks/Python.framework to /System/Frameworks/Python.framework). My idea was to keep the /System/Library/Frameworks files to be used by system commands in /usr/bin, and have /usr/local/bin points to another “user land” install in /Library/Frameworks. In order to do that :

rename /System/Library/Framework/Python.framework into _OLD_Python.framework
delete every python file in /usr/local/bin (using sudo rm /usr/local/bin/python*) and /usr/local/bin/pip* (but do NOT touch /usr/bin) Waitress the musical libretto.
Reinstall python from the official site (http://www.python.org/getit/)
> This will reinstall python in /Library/Framework and not /System/Library/Framework
Then launch the Applications/Python/Update Shell Profile.command command that will make sure your path is using that one Yoot tower mac.
Then recreate the symlinks in /usr/local/bin using
ln -s ././Library/Frameworks/Python.framework/Versions/2.7/bin/python python
Finaly, rename the _OLD_Python.framework back to Python.framework (because that’s the path /usr/bin/python points to)

Typing “which python” should point to /Library/… and not /System/Library. From there you should be able to reinstall easy_install and pip properly.

Solution no. 6:

Rather than change ownership, it is possible to simply change permissions:

$ sudo chmod -R o+rX /Library/Python/2.7/site.packages

Solution no. 7:

On Mavericks, I found that

while pip showed

I renamed the old pip and created a symlink to the proper pip binary, and now all is well. It’s probably not the best solution, but it works.

Solution no. 8:

Pip Install To Python 2.7

I fixed this by reinstalling python with homebrew: brew install python

Solution no. 9:

I changed the permissions for Python folder (from root to my user), and now everything work for me:

Not recommended for machines with multiple users.

Solution no. 10:

I usually had same issue with some project referencing bonjour-py in their requirements.txt, didn’t know which or how to track that one at the moment.

And someone told me that pip-tool. It’s actually a great alternative to identify which you have, and if you want to update them. And as a bonus it ignored well the bonjour-py error.

Os X Pip For Python 32

Hope this helps!