[Python-Dev] [Python-checkins] peps: Revise PEP 453 to be docs-only for 2.7 & 3.3

[Nick Coghlan]

On 11 Oct 2013 05:04, "Terry Reedy" <tjreedy at udel.edu> wrote:
>
> On 10/10/2013 10:48 AM, nick.coghlan wrote:
>>
>> http://hg.python.org/peps/rev/405b80d54b7d
>> changeset:   5188:405b80d54b7d
>> user:        Nick Coghlan <ncoghlan at gmail.com>
>> date:        Fri Oct 11 00:47:47 2013 +1000
>> summary:
>>    Revise PEP 453 to be docs-only for 2.7 & 3.3
>>
>> - all functional changes are now 3.4 only
>> - still proposes docs changes for 2.7 & 3.3
>> - notes current effort to create a Windows installer for pip
>> - notes possibility of a future PEP to provide a combined
>>    CPython 2.7, pip and Python Launcher installer from python.org
>
>
>> +`Installing Python Modules <http://docs.python.org/3/install>`__ guide
in
>> +Python 2.7, 3.3 and 3.4 be updated to officially recommend the use of
``pip``
>> +as the default installer for Python packages, and that appropriate
technical
>> +changes be made in Python 3.4 to provide ``pip`` by default in support
of
>> +that recommendation.
>
>
> Does one need a separate installation of pip for each Python version or
is pip 'separate' enough that one installation works for all Python
versions? Is the answer to this the same on all systems? If the answer is
'one' and 'yes', the 2.7 and 3.3 docs should say that installing 3.4 also
installs pip and that this is all one needs to do.

pip is version specific (it's just a normal Python package).

>> +While this PEP only proposes documentation changes for Python 2.7, once
>> +``pip`` has a Windows installer available, a separate PEP will be
created
>> +and submitted proposing the creation and distribution of aggregate
installers
>> +for future CPython 2.7 maintenance releases that combine the CPython,
>> +``pip`` and Python Launcher for Windows installers into a single
download
>> +(the separate downloads would still remain available - the aggregate
>> +installers would be provided as a convenience, and as a clear indication
>> +of the recommended operating environment for Python in Windows systems).
>
>
> If the combined installer is an optional convenience, I would not think a
PEP necessary. I am assuming that the combined installer would not add a
module to /lib any more than two separate installers would, and hence would
not be adding a feature to 2.7 itself.

That PEP (if created) would be for publishing such an aggregate installer
from the 2.7 release page on python.org.

Since it would be proposing more work for the creator of the CPython
Windows installers, a PEP seems appropriate.

Cheers,
Nick.

>
> --
> Terry Jan Reedy
>
> _______________________________________________
> Python-checkins mailing list
> Python-checkins at python.org
> https://mail.python.org/mailman/listinfo/python-checkins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20131011/e2189c0f/attachment.html>