pip vs python -m pip?
On 21/06/2019 15.27, Malcolm Greene wrote:
> 64-bit Python 3.6.8 running on Windows with a virtual environment activated.
> "pip -v" reports 19.0.3
> "python -m pip" reports 19.1.1
> Is this behavior by design or a bug?
If the pip and python executables you're calling both live in the
virtual environment, then it might be a bug
> My takeaway is that its better to run "python -m pip ..." vs "pip ..." when running pip related tasks.
It's a good rule of thumb. When you have multiple versions of Python
installed side-by-side, there can be a danger that you call the wrong
'pip' by accident.
I don't think this should be a concern in a virtual environment though