System PIP instead of virtualenv PIP by default?

Question

After using virtualenv with pip off-and-on for a couple of days, I\'ve found that the version of PIP that is used after the virtualenv is actived is the global PIP instead o

Answer 1

When you create a virtualenv, the activate file hardcodes the variable VIRTUAL_ENV to the location in which you first created the root directory. This variable is then exported when you source /bin/activate.

Consequently, if you move the virtualenv directory subsequent to its creation, the hardcoded file path will be incorrect.

Just open /bin/activate in a text editor and make sure VIRTUAL_ENV is set to the new path of your virtualenv directory:

VIRTUAL_ENV="/Full/path/to/"
export VIRTUAL_ENV

before running source /bin/activate again.

Then of course you can test the version of pip with which pip which should produce:

/Full/path/to//bin/pip

rather than /usr/bin/pip or /bin/pip etc.