Do you use virtualenv or something to manage different environments? That's the achilles heel of vanilla pip for me, having everything pollute global installs is not so cute.
"venv" (the modern version of virtualenv) is included in python3 out of the box¹ now, so creating a virtualenv is as simple as `python3 -m venv venv`. (I usually do use one to avoid polluting the global one / I let the system package manager manage the global install.)
¹but note that Debian & Debian derivatives shove several standard library modules into individual packages, so you might need to apt-get install more than just python3.
Absolutely. You should almost never be pip-installing global things (of course there are circumstances, but you should know exactly why you are choosing to do it, vs an env).
Vanilla pip works well with the venv module. I still manually manage the majority of my virtual environments, with the virtualenvwrapper libary, although `source path/to/myvenv/bin/activate` also works.
