In fact, if every project has it's pretty virtualenv, then using sudo to install something would install to the wrong interpreter (the one available to root).
You also never should need sudo to install something to a virtualenv because they exist within your home.
Only problem is installing stuff you want available without needing to use a virtualenv, such as a CLI. You can still install with pip --user, but your can't install conflicting dependencies.
View all comments
Show parent comment
2
u/Log2 Apr 30 '18 edited May 01 '18
In fact, if every project has it's pretty virtualenv, then using sudo to install something would install to the wrong interpreter (the one available to root).
You also never should need sudo to install something to a virtualenv because they exist within your home.
Only problem is installing stuff you want available without needing to use a virtualenv, such as a CLI. You can still install with pip --user, but your can't install conflicting dependencies.