This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients Justin.Engel, Marcus.Smith, dstufft, eryksun, ncoghlan, paul.moore, r.david.murray, vinay.sajip
Date 2014-10-05.02:31:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Also reducing the priority back to "normal" - the docs at already specifically recommend the "python -m pip" spelling because it's the most universal.

Calling "pip" directly is known to fail in a variety of situations. For example, at system level on *nix systems, it invokes the Python 2 version - you have to call "pip3" to get the Python 3 version. On Windows, if the Scripts directory isn't on PATH, calling pip directly also doesn't work.

This bug just adds another scenario to that existing list.

(I filed to suggest also making the "pip -> python -m pip" switch in PyPUG examples)
Date User Action Args
2014-10-05 02:31:34ncoghlansetrecipients: + ncoghlan, paul.moore, vinay.sajip, r.david.murray, eryksun, dstufft, Marcus.Smith, Justin.Engel
2014-10-05 02:31:34ncoghlansetmessageid: <>
2014-10-05 02:31:34ncoghlanlinkissue21699 messages
2014-10-05 02:31:33ncoghlancreate