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 paul.moore
Recipients dstufft, ncoghlan, paul.moore
Date 2014-01-06.10:36:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389004595.51.0.303248047302.issue20139@psf.upfronthosting.co.za>
In-reply-to
Content
The Python 3.4b2 installer for Windows does not install a "pip.exe" wrapper when the default options are selected. Only the "pip3.exe" and "pip3.4.exe" commands are provided.

The documentation for ensurepip makes it clear that this is the default behaviour, but there is no comment in either the PEP or in "Python Setup and Usage" stating that this is what happens. Also, I imagine that people will expect a "pip" command to be available by default, so an explanation of *why* only the versioned commands are installed should be added.

(It may be that having the unversioned command as well is actually the correct thing to do, on Windows if not on Unix - I can't recall the details of the discussion. If so, maybe the correct thing to do is to change the Windows installer behaviour).
History
Date User Action Args
2014-01-06 10:36:35paul.mooresetrecipients: + paul.moore, ncoghlan, dstufft
2014-01-06 10:36:35paul.mooresetmessageid: <1389004595.51.0.303248047302.issue20139@psf.upfronthosting.co.za>
2014-01-06 10:36:35paul.moorelinkissue20139 messages
2014-01-06 10:36:35paul.moorecreate