4 ms·
When I was running the developer version of Mavericks, the site_packages weren't preserved, which meant pip & setuptools were broken, so I had to reinstall them
by huxley 13y ago
When I was running the developer version of Mavericks, the site_packages weren't preserved, which meant pip & setuptools were broken, so I had to reinstall them like so:
http://www.pip-installer.org/en/latest/installing.html http://www.pip-installer.org/en/latest/installing.html
then upgrading pip and virtualenvwrapper:
$ sudo easy_install pip
$ sudo pip install --upgrade virtualenvwrapper
If that doesn't do the trick, you might need to install the Xcode command line tools.
[update: oh well, it looks like the parent deleted the question, but for posterity, it dealt with problems with virtualenvwrapper and pip after upgrading to Mavericks]
- mhurron 13y agoWouldn't it be better to not install eggs into the system path and instead into site-packages on a per-user basis? Or, quite frankly, not use the system python at all?
- huxley 13y agoSure ideally, I've played with pyenv a bit but for my main machine I've kept my systemwide installs down to just enough to run virtualenv and virtualenvwrapper (everything else lives inside virtualenvs). For several situations though (like when Xcode command line tools stops working after a major OS update) it won't matter. You need a c compiler for several packages and having your stuff isolated per-user or using a non-system Python won't help that one bit.