Open woile opened 10 years ago
Thanks for comment this! The virtualenvwrapper's script have to be loaded in the shell statup file in order to work properly. The issue is the location of that script, because it change on each machine so we can not guess where is it located. "dotfiles" does not try to load "virtualenvwrapper". You could add the following lines in your "~/.bash_local", which is loaded by "dotfiles" at the end of the initialization and contains machine's specific configration.
# ...
#Place where you save your environments
export WORKON_HOME=$HOME/virtualenv
#Load virtualenvwrapper itself!
source /fullpath/to/virtualenvwrapper.sh
As you pointed, you have to add the lines above in order to load script. To get further informacion about the configuration to can go to virtualenvwrapper Install guide
Thinking about this, I have realized that our version of "cd" should to be modified to keep working even if the user is not using "virtualenvwrapper" and enter to a folder with the ".venv" file. What do you think?
The option I like the most is to let cd
keep working, and after installing the script, prompting a message saying something like this:
"If you want to have xxxx functionality, please add the following lines to your bashrc:
# ...
#Place where you save your environments
export WORKON_HOME=$HOME/virtualenv
#Load virtualenvwrapper itself!
source /fullpath/to/virtualenvwrapper.sh
"
Installed dotfiles in my notebook, i was using workon command with no problems, now it's missing, when trying to load venv automatically, this appeared: Found .venv in directory. Calling: workon music_taste bash: workon: command not found
I think it's missing the following:
virtualenvwrapper
export WORKON_HOME=$HOME/virtualenv source /usr/local/bin/virtualenvwrapper.sh
or smoething like that, for me it's working now.