-
-
Save stringertheory/fb70af00f0ed09c5c004 to your computer and use it in GitHub Desktop.
put this in .bashrc to change to environments created with virtualenvwrapper automatically
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Call virtualenvwrapper's "workon" if .venv exists. This is modified from-- | |
# http://justinlilly.com/python/virtualenv_wrapper_helper.html | |
# which is linked from-- | |
# http://virtualenvwrapper.readthedocs.org/en/latest/tips.html#automatically-run-workon-when-entering-a-directory | |
check_virtualenv() { | |
if [ -e .venv ]; then | |
env=`cat .venv` | |
if [ "$env" != "${VIRTUAL_ENV##*/}" ]; then | |
echo "Found .venv in directory. Calling: workon ${env}" | |
workon $env | |
fi | |
fi | |
} | |
venv_cd () { | |
builtin cd "$@" && check_virtualenv | |
} | |
# Call check_virtualenv in case opening directly into a directory (e.g | |
# when opening a new tab in Terminal.app). | |
check_virtualenv | |
# Add the following to ~/.bash_aliases: | |
# alias cd="venv_cd" | |
# also, for fun, add something like `pyfiglet "env : $1"` to ~/.virtualenv/preactivate | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How is this different from autoenv? as in http://docs.python-guide.org/en/latest/dev/virtualenvs/