History

Jay Tavares 1a0500b00d Change order of automatic virtualenv activation/deactivation (#6687 ) When navigating from a virtualenv project directory, first deactivate the virtualenv. Then, check to see if destination directory is also a virtualenv project directory. If it is activate that virtualenv. See #5817.		2019-12-20 21:08:03 -08:00
..
README.md	…
virtualenvwrapper.plugin.zsh	Change order of automatic virtualenv activation/deactivation (#6687 )	2019-12-20 21:08:03 -08:00

README.md

Virtualenvwrapper plugin

This plugin loads Python's virtualenvwrapper shell tools.

To use it, add virtualenvwrapper to the plugins array in your zshrc file:

plugins=(... virtualenvwrapper)

Usage

The plugin allows to automatically activate virtualenvs on cd into git repositories with a matching name:

➜  github $ cd ansible
(ansible) ➜  ansible git:(devel) $ cd docs
(ansible) ➜  docs git:(devel) $ cd ..
(ansible) ➜  ansible git:(devel) $ cd ..
➜  github $

We can override this by having a .venv file in the directory containing a differently named virtualenv:

➜  github $ cat ansible/.venv
myvirtualenv
➜  github $ cd ansible
(myvirtualenv) ➜  ansible git:(devel) $ cd ..
➜  github $

We can disable this behaviour by setting DISABLE_VENV_CD=1 before Oh My Zsh is sourced:

DISABLE_VENV_CD=1
plugins=(... virtualenvwrapper)
source $ZSH/oh-my-zsh.sh