Activating virtualenvs isn't necessary. In every python project I work in, I do $ cd projectFoo $ ./ve/bin/python whatever... (more realistically, it'

Activating virtualenvs isn't necessary. In every python project I work in, I do $ cd projectFoo $ ./ve/bin/python whatever... (more realistically, it's `make whatever` which then builds the virtualenv into `./ve` if needed, pip installs required packages into it, and runs the command). Yes, I agree that it would be nice if the default behaviour of `pip install -r requirements.txt` was to install it in an isolated virtualenv specific to that project, but it's not also not like it's completely impossible magic.