PEP 453 post date and wording tweak
This commit is contained in:
parent
2679eb0c91
commit
e6cc2772ac
12
pep-0453.txt
12
pep-0453.txt
|
@ -10,7 +10,7 @@ Type: Process
|
|||
Content-Type: text/x-rst
|
||||
Created: 10-Aug-2013
|
||||
Post-History: 30-Aug-2013, 15-Sep-2013, 18-Sep-2013, 19-Sep-2013,
|
||||
23-Sep-2013, 29-Sep-2013
|
||||
23-Sep-2013, 29-Sep-2013, 13-Oct-2013
|
||||
|
||||
|
||||
Abstract
|
||||
|
@ -279,13 +279,9 @@ environments using the standard library's ``venv`` module via the
|
|||
To support that end, this PEP proposes the inclusion of an ``ensurepip``
|
||||
bootstrapping module in Python 3.4, as well as automatic invocation of that
|
||||
module from ``pyvenv`` and changes to the way Python installed scripts are
|
||||
handled on Windows.
|
||||
|
||||
To clearly demarcate development responsibilities, and to avoid
|
||||
inadvertently downgrading ``pip`` when updating CPython, the proposed
|
||||
mechanism to achieve this is to include an explicit `pip`_ bootstrapping
|
||||
mechanism in the standard library that is invoked automatically by the
|
||||
CPython installers provided on python.org.
|
||||
handled on Windows. Using a bootstrap module rather than providing ``pip``
|
||||
directly helps to clearly demarcate development responsibilities, and to
|
||||
avoid inadvertently downgrading ``pip`` when updating CPython.
|
||||
|
||||
To provide clear guidance for new users of Python that may not be
|
||||
starting with the latest release, this PEP also proposes that the
|
||||
|
|
Loading…
Reference in New Issue