virtualenv "workon" doesn't work

Asked 27/4, 2015 at 15:36 Answered 23/3, 2016 at 15:32

Solved python django virtualenv virtualenvwrapper

I made a virtualenv environment for a project. "workon projectname" worked and activated the environment but after I shut down my laptop it starts not working. Could someone tell me how to fix this?

Covert answered 27/4, 2015 at 15:36 Comment(1)

There is nowhere near enough information to tell you what's wrong. You haven't even told us what OS you're using! Have you followed e.g. this step? – Coffman 27/4, 2015 at 15:43

Since I don't have enough reputation to comment I'll simply attempt an answer as I think I know what the issue is.

Firstly, if you could provide more details as to what you mean by "not working" I will edit my answer if need be and attempt to help more.

Typically this happens because virtualenvwrapper is a shell script that needs to be sourced before you have access to commands like "workon" and "mkvirtualenv". My virtualenvwrapper.sh script is installed in /usr/local/bin so I simply run:

$ source /usr/local/bin/virtualenvwrapper.sh

Typically I add this line to my ~/.bashrc or ~/.profile file to ensure these commands are always available in the shell. You can find more specific information for your setup in the Installation Documentation. Not having it sourced would definitely cause the commands to stop working after a shutdown.

Drouin answered 27/4, 2015 at 15:45 Comment(7)

Thanks, Eric! I ran the code "source /usr/local/bin/virtualenvwrapper.sh" but it it gave me the below error. mkdir: /opt/virtual_env/: Permission denied Also, I included the code in .bashrc and .profile. It seems that it didn't work. – Covert 27/4, 2015 at 16:7

It sounds like you may have created the virtualenv as another user or as root. Let me know if running the following command helps: $ sudo chown -R youruser:youruser /opt/virtual_env – Drouin 27/4, 2015 at 19:8

Thanks again :) I ran the command but I got the error below. chown: youruser: illegal group name – Covert 27/4, 2015 at 22:20

You should replace youruser with your actual username, that was just a placeholder value I used. – Drouin 29/4, 2015 at 0:41

Thanks again but I still get illegal group name.. Would you still have other ideas to fix? – Covert 2/5, 2015 at 6:50

You might just try $ sudo chown -R youruser /opt/virtual_env – Drouin 4/5, 2015 at 2:49

Virtualenwrapper was working earlier for my case but yesterday I've made some additions to .bashrc file to get a project which required pyenv and saw the suspect immediately once I opened the file. pyenv virtualenv-init conflicts with this – Vanderhoek 1/6, 2022 at 8:57

In my case I need to do the following steps (on Mac OS X 10.11):

I added this line:

source "/Library/Frameworks/Python.framework/Versions/2.7/bin/virtualenvwrapper.sh"

to my ~/.bash_profile

And afterwards, following Eric Scrivner instructions, I created a folder at /opt/ called virtual_env using sudo mkdir /opt/virtual_env

And finally, I run the command sudo chown -R youruser /opt/virtual_env

And than: source ~/.bash_profile

Tonyatonye answered 23/3, 2016 at 15:32 Comment(0)

Recommended topics

Hot tags