[Python-Dev] Backporting ensurepip to 2.7, Which commands to install?

Nick Coghlan ncoghlan at gmail.com
Wed Oct 22 13:45:31 CEST 2014

On 22 October 2014 21:10, Geoffrey Spear <geoffspear at gmail.com> wrote:
> On Wed, Oct 22, 2014 at 6:15 AM, Pekka Klärck <peke at iki.fi> wrote:
>> I just installed Python 3.4.2 on Windows and noticed that its Scripts
>> directory has these files out-of-the-box:
>> easy_install.exe
>> easy_install-3.4.exe.
>> pip.exe
>> pip3.exe
>> pip3.4.exe
>> Based on Nick's explanation above, having pip.exe there looks like bug
>> in the installer and could easily cause a conflict with other pip
>> installations. I don't understand why easy_install is included there
>> in the first place, but easy_install.exe can obviously cause a similar
>> conflict.
> Nick's explanation is based on PEP 394, which explicitly does not
> apply to Windows. The Windows Python executables are called
> "python.exe" and "pythonw.exe"; no "3" has ever been part of the name
> and it's not surprising that there's a matching "pip.exe". The
> pip3.exe and pip3.4.exe being installed are actually the anomalies
> here, but I wouldn't call them a bug.

Right, the design on Windows is a little different, as the Python 3
executable has always remained "python.exe" there. Originally we
followed PEP 394 style naming on Windows as well, but then realised
during the 3.4 beta cycle that doing so didn't actually make sense
(see http://bugs.python.org/issue20568 and


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list