CODEWITHSUNDEEP
pythonvirtualenv
rfj001
rfj001

Reputation: 8518

Virtualenv All Messed Up - Segmentation Fault: 11

I'm a little worried right now I may have majorly messed things up for myself... but here's what happened:

After upgrading to OSX Yosemite I was having issues with my Python installation, so I reinstalled using brew python and brew python3. My previous installations were not installed through homebrew. After this, I began having problems with python packages I had previously installed, namely pip, virtualenv, and virtualenvwrapper. I messed around with things for a while, deleted the pre-existing Python framework in /Library and uninstalled and reinstalled the three packages to get them all working with the new, homebrewed python I'm running.

Now, when I open a virtualenv that I had created prior to this whole ordeal and try to run any commands from any python package (like pip freeze or ./manage.py runserver), I get Segmentation Fault: 11

Does anyone know why I am getting this error or how I can fix it?

EDIT Also while the virtualenv experts are here... is there a way that I can make my python version for virtualenv default to python3?

Upvotes: 1

Views: 2305

Answers (1)

Tim
Tim

Reputation: 43384

Many things could be the cause of the error, I'm not even going to try and guess.

Because you have been messing around a lot, I'd say the easiest and maybe best option would be to just recreate your virtualenv

is there a way that I can make my python version for virtualenv default to python3?

Default for all venvs, I don't know. But you can make a new virtualenv with python 3.x with this command

$ virtualenv -p /usr/bin/python3 virtualenv_name

Upvotes: 1

Related Questions