pip vs python -m pip?
On Fri, Jun 21, 2019 at 11:55 PM Malcolm Greene <python at bdurham.com> wrote:
> > you must be picking up pip from a different python install (or virtualenv) than you are picking up python.
> > Check your %PATH%
> That was our first guess. Only one version of Python installed on the system (we install on an empty, freshly serviced pack Windows VM). Only one version of python*.exe found via Explorer.
> This behavior observed across multiple Windows 2016 Enterprise servers and Windows 10 Professional desktops.
Well, I'm pretty confident this isn't an actually desired behaviour,
so to answer your original question, I'd say "bug" is the more
accurate choice. That said, though... there are a LOT of ways that the
Windows path can fail to pick up the correct 'pip'. Normally
activating a venv should let you use "pip" to mean the right thing
just as "python" does, but maybe something's cached?
Are you doing this in cmd.exe, powershell, bash, or some other shell?