Re: pip vs python -m pip?

2019-06-21 Thread Skip Montanaro
Malcolm> Running pip as a package (python -m pip) will force the use of the virtual env copy of pip. Running pip as an application vs package may use the system version of pip. I believe it is for just this reason that the recommended spelling these days is "python -m pip". Skip -- https://mail.

Re: pip vs python -m pip?

2019-06-21 Thread Malcolm Greene
> From: Chris Angelico > Are you doing this in cmd.exe, powershell, bash, or some other shell? Same result via cmd.exe and PowerShell (ps1). > 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 r

Re: pip vs python -m pip?

2019-06-21 Thread Chris Angelico
On Fri, Jun 21, 2019 at 11:55 PM Malcolm Greene 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 e

Re: pip vs python -m pip?

2019-06-21 Thread Thomas Jollans
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

Re: pip vs python -m pip?

2019-06-21 Thread Malcolm Greene
> 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*

Re: pip vs python -m pip?

2019-06-21 Thread Bill Deegan
you must be picking up pip from a different python installl (or virtualenv) than you are picking up python. Check your %PATH% On Fri, Jun 21, 2019 at 6:29 AM Malcolm Greene wrote: > 64-bit Python 3.6.8 running on Windows with a virtual environment > activated. > > "pip -v" reports 19.0.3 > "pyth

pip vs python -m pip?

2019-06-21 Thread Malcolm Greene
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? My takeaway is that its better to run "python -m pip ..." vs "pip ..." when running pip related tasks. Thoughts? Malcolm --