söndag 14 augusti 2016

workon not found

virtualenvwrapper is handy for admin of envs. But some times workon is not longer recognized by the shell - workon: command not found.

A dirty way to handle this is to use the path of the virtual env. For mopidy I use:

source ~/Env/mopidy/bin activate

Deactivate as usaul with deactivate.

There is a SO discussion about this, see here.

A BETTER way is to add some info to ~/.bashrc as explained in the docs.
# load virtualenvwrapper for python
export WORKON_HOME=$HOME/Envs
export PROJECT_HOME=$HOME/mopidy-dev
source /usr/local/bin/virtualenvwrapper.sh

Folder Env will contain the virtual envs.

Inga kommentarer:

Skicka en kommentar