[butwhywhyoh]

I mean, this is generally good advice, but this reads like an infomercial where they show someone struggling REALLY hard to boil water to make a pot of spaghetti, when we all know it's really not that hard.

They try to make finding your pip executable sound difficult, and even more difficult would be to understand what interpreter its tied to. Except...

> pip -V

> # pip 19.0.3 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)

I'm all for evangelizing best practices, but let's at least be honest about it.

[psyklic]

I think the point is that most people just immediately type `pip install ...`, without thinking about which interpreter it's tied to.

It's fairly common for beginners to tell me they installed something using pip, then the Python interpreter can't find the package.

[bornfreddy]

This. Also, the argument is a bit weird:

- always use python -m pip

- if in venv, it doesn't do any good, but do it anyway for consistency

- you should also use venv

So... Maybe just always use virtual env and then you can use just pip?

[Hackbraten]

While it’s good advice to use a venv for development work, there are a couple of Python packages that you want to have installed globally, such as pip, pipenv or poetry. So I don’t see a contradiction here after all.