Terminal: Where is the shell start-up file?

You’re probably using bash so just add these 3 lines to ~/.bash_profile: $ cat >> ~/.bash_profile export WORKON_HOME=$HOME/.virtualenvs export PROJECT_HOME=$HOME/directory-you-do-development-in source /usr/local/bin/virtualenvwrapper.sh ^D where ^D means you type Control+D (EOF). Then either close your terminal window and open a new one, or you can “reload” your .bash_profile like this: $ source ~/.bash_profile

Virtualenv uses wrong python, even though it is first in $PATH

My problem was that i recently moved my project with virtualenv to another location, due to this activate script had wrong VIRTUAL_ENV path. $ cat path_to_your_env/bin/activate … # some declarations VIRTUAL_ENV=”/path_to_your_env/bin/python” # <– THIS LINE export VIRTUAL_ENV … # some declarations To fix this, just update VIRTUAL_ENV in activate script. Also you maybe need to …

Read more

Install virtualenv and virtualenvwrapper on MacOS

To install virtualenv and virtualenvwrapper for repetitive use you need a correctly configured Python (this example uses Python 3.x but process is identical for Python 2.x). Although you can get python installer from Python website I strongly advice against it. The most convenient and future-proof method to install Python on MacOS is brew. Main difference …

Read more

Installed virtualenv and virtualenvwrapper: Python says no module named virtualenvwrapper

I’ve managed to get this working after having the same problem you’ve described here by editing my ~/.bash_profile and adding this: export WORKON_HOME=$HOME/code/.virtualenvs export PROJECT_HOME=$HOME/code export VIRTUALENVWRAPPER_PYTHON=/usr/local/bin/python export VIRTUALENVWRAPPER_VIRTUALENV=/usr/local/bin/virtualenv export VIRTUALENVWRAPPER_VIRTUALENV_ARGS=’–no-site-packages’ source /usr/local/bin/virtualenvwrapper.sh Save, close. then: $ source ~/.bash_profile and: $ mkvirtualenv test