Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Star 9 You must be signed in to star a gist
  • Fork 3 You must be signed in to fork a gist
  • Save Willyfrog/3226639 to your computer and use it in GitHub Desktop.
Save Willyfrog/3226639 to your computer and use it in GitHub Desktop.
virtualenv-auto-activate-auto-deactivate
#!/bin/bash
# virtualenv-auto-activate.sh
#
# Installation:
# Add this line to your .bashrc or .bash-profile:
#
# source /path/to/virtualenv-auto-activate.sh
#
# Go to your project folder, run "virtualenv .venv", so your project folder
# has a .venv folder at the top level, next to your version control directory.
# For example:
# .
# ├── .git
# │ ├── HEAD
# │ ├── config
# │ ├── description
# │ ├── hooks
# │ ├── info
# │ ├── objects
# │ └── refs
# └── .venv
# ├── bin
# ├── include
# └── lib
#
# The virtualenv will be activated automatically when you enter the directory.
_virtualenv_auto_activate() {
if [ -e ".venv" ]; then
# Check to see if already activated to avoid redundant activating
if [ "$VIRTUAL_ENV" = "" ]; then
_VENV_NAME=$(basename `pwd`)
echo Activating virtualenv \"$_VENV_NAME\"...
VIRTUAL_ENV_DISABLE_PROMPT=1
source .venv/bin/activate
_OLD_VIRTUAL_PS1="$PS1"
PS1="($_VENV_NAME)$PS1"
export PS1
fi
else
if [ "$VIRTUAL_ENV" != "" ]; then
echo deactivating VirtualEnv
deactivate
fi
fi
}
export PROMPT_COMMAND=_virtualenv_auto_activate
@MartinVincent
Copy link

Hi,

Good stuff, but I would suggest adding a variable (ie: VENV_DIR='.venv') and refer to it at lines 28 and 34. Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment