Problem with virtualenv in Mac OS X

前端 未结 14 2051
情歌与酒
情歌与酒 2020-12-23 16:29

I\'ve installed virtualenv via pip and get this error after creating a new environment:

selenium:~ auser$ virtualenv new  
New pyt         


        
相关标签:
14条回答
  • 2020-12-23 17:22

    I had the same problem and as I see it now, it was caused by a messy Python installation. I have OS X installed for over a year since I bought a new laptop and I have already installed and reinstalled Python for several times using different sources (official binaries, homebrew, official binaries + hand-made adjustments as described here). Don't ask me why I did that, I'm just a miserable newbie believing everything will fix itself after being re-installed.

    So, I had a number of different Pythons installed here and there as well as many hardlinks pointing at them inconsistently. Eventually I got sick of all of them and reinstalled OS X carefully cleaned the system from all the Pythons I found using find utility. Also, I have unlinked all the links pointing to whatever Python from everywhere. Then I've installed a fresh Python using homebrew, installed virtualenv and everything works as a charm now.

    So, my recipe is:

    sudo find / -iname "python*" > python.log

    Then analyze this file, remove and unlink everything related to the version of Python you need, reinstall it (I did it with homebrew, maybe official installation will also work) and enjoy. Make sure you unlink everything python-related from /usr/bin and /usr/local/bin as well as remove all the instances of Frameworks/Python.framework/Versions/<Your.Version> in /Library and /System/Library.

    It may be a dirty hack, but it worked for me. I prefer not to keep any system-wide Python libraries except pip and virtualenv and create virtual environments for all of my projects, so I do not care about removing the important libraries. If you don't want to remove everything, still try to understand whether your Pythons are, what links point to them and from where. Then think what may cause the problem and fix it.

    0 讨论(0)
  • 2020-12-23 17:25

    I also had this problem, and I tried the following method which worked for me:

    conda install virtualenv
    

    virtualenv --system-site-packages /anaconda/envs/tensorflow (here envs keeps all the virtual environments made by user)

    source /anaconda/envs/tensorflow/bin/activate
    

    Hope it's helpful.

    0 讨论(0)
提交回复
热议问题