Message228529
| 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 |
<1412476294.52.0.260801819343.issue21699@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Also reducing the priority back to "normal" - the docs at https://docs.python.org/3/installing/ 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 https://github.com/pypa/python-packaging-user-guide/issues/107 to suggest also making the "pip -> python -m pip" switch in PyPUG examples) |
|