why does virtualenv workon not take me to the env directory

Question

I have virtualenv setup and it is working well accept for one annoying issue. when I use the workon command to enter an environment the environment is logs in correctly but I do not get automatically directed to the environments root directory.

I have added the following lines to my .bashrc file:

export WORKON_HOME=$HOME/.virtualenvs
source /usr/local/bin/virtualenvwrapper.sh

and reloaded it (source .bashrc), but when I enter an environment I am still left in my ubuntu user home directory. I have also tries restarting my server, but still no luck.

score 7 · Accepted Answer · answered Aug 25 '12 at 10:12

7

I don't think workon changes to the environment directory. The solution would is to put that in postactivate file of your virtualenv.

E.g. I have following in my <virtual_env_dir>/bin/postactivate

cd /home/myuser/work/

answered Aug 25 '12 at 10:12

Rohan

52,392
12
90
87

See @Casebash 's solution using ```setvirtualenvproject```. – fbicknel Aug 08 '18 at 18:32

score 4 · Answer 2 · answered May 09 '14 at 06:22

4

Environments are separate from projects with virtualenvwrapper. You first need to ensure that the $PROJECT_HOME variable is set. Then you can use the mkproject command to create an environment and a project in `$PROJECT_HOME'. Alternatively, you can use setvirtualenvproject to associate an existing project with an existing virtual environment.

answered May 09 '14 at 06:22

Casebash

114,675
90
247
350

With this solution, to switch into the virtualenv, you'd need to `workon && cdproject`. – Steven Maude Feb 10 '15 at 13:59
Not if you use ```setvirtualenvproject ``` That worked perfectly for me. – fbicknel Aug 08 '18 at 18:30

why does virtualenv workon not take me to the env directory

2 Answers2