[Distutils] What does it mean for Python to "bundle pip"?

[Nick Coghlan]

On 19 August 2013 10:08, Paul Moore <p.f.moore at gmail.com> wrote:
> 2. We need to be careful to define exactly when and how the "pip" command is
> present. Don't forget that on Windows, the "python" command is not on PATH
> by default (and the existence of the launcher means that it really doesn't
> need to be). I would suggest that we say something like "The pip command
> will be installed alongside the python command, and will be available when
> python is"[1]. We should also probably note that versioned variants of pip
> will be provided matching the versioned copies of the python command that
> are available (e.g., pip3/pip3.4 on Unix, maybe none at all on Windows...).
> Unless of course we want to use a different scheme for pip, in which case we
> need to agree on what that will be.

In 3.3+, I believe the Windows installer does PATH modification by
default. In 3.4+ it will likely do PATHEXT modification, too.

> 3. This also begs the question of whether pip.exe gets installed in the
> "Scripts" subdirectory on Windows, as at present - if it does, we'll have to
> be very careful indeed over how we word the instructions, as it's *easy* for
> users to have python.exe on PATH but not have Scripts\pip.exe on there :-(

We should just add Scripts to the PATH in the installer as well.

Cheers,
Nick.

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