➜

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 dstufft, larry, loewis, ncoghlan, paul.moore
Date 2014-02-09.00:08:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391904485.94.0.961786946534.issue20568@psf.upfronthosting.co.za>
In-reply-to
Content 
Installing 3.4b3 on Windows to test issue 20053, I was surprised to find that after installation, "pip install <package>" didn't work.

I had forgotten that due to the flat executable namespace on POSIX systems, we only install pip3 and pip3.4 by default - you have to pass "--default-install" to ensurepip to get it to install the unqualified "pip".

For virtual environments, we handle that in the venv module - it passes "--default-pip" when invoking the ensurepip CLI.

Given that Windows uses "python" for both Python 2 & 3 (in contrast to the POSIX python/python3 and python2/python3 conventions), perhaps we should be passing --default-install to ensurepip in the Windows installers as well?
History
Date User Action Args
2014-02-09 00:08:06ncoghlansetrecipients: + ncoghlan, loewis, paul.moore, larry, dstufft
2014-02-09 00:08:05ncoghlansetmessageid: <1391904485.94.0.961786946534.issue20568@psf.upfronthosting.co.za>
2014-02-09 00:08:05ncoghlanlinkissue20568 messages
2014-02-09 00:08:05ncoghlancreate