Should I be creating a virtual environment for each project?

Viewed 8837

After googling around regarding virtualenv, I was under the impression that virtual environments should be created for every project I create (that are related and use the same site packages).

Is this true and why or why not?

Also, if I am currently using a virtualenv for one of my projects, how would I go about upgrading when upgrades for the packages come along?

4 Answers

According to this post, https://rushter.com/blog/python-virtualenv/

Only the python interpreter (executable) and a few things like pip, easy_install are copied to the local directory for your venv project. All the standard library files, such as io, random, struct ... are linked from your venv directory, not copied. So your disk space will not be going up quickly.

Related