For those of you who install your virtual environments into a global directory (e.g. virtualenvwrapper users, `$WORKON_HOME`), what's the primary reason you do that instead locally into your workspace (e.g. `.venv` directory next to your code)?
@brettcannon I was annoyed when I forgot to activate venv in terminal, or switch to another one. So I wrote a simple tool for activating and deactivating venv automatically basen on current path. And I just decided to keep all those venvs in one place.
Brett Cannon
Dawid
