More PEP 453 cleanups
This commit is contained in:
parent
d4fc58c7e7
commit
6482692ff6
|
@ -270,8 +270,7 @@ This PEP proposes that the
|
|||
`Installing Python Modules <http://docs.python.org/3/install>`__ guide be
|
||||
updated to officially recommend the use of ``pip`` as the default
|
||||
installer for Python packages, rather than the current approach of
|
||||
recommending the direct invocation of the ``setup.py install`` ``distutils``
|
||||
command.
|
||||
recommending the direct invocation of the ``setup.py install`` command.
|
||||
|
||||
However, to avoid recommending a tool that CPython does not provide, it is
|
||||
further proposed that the `pip`_ package manager be made available by
|
||||
|
@ -281,8 +280,9 @@ utility).
|
|||
|
||||
To support that end, this PEP proposes the inclusion of an ``ensurepip``
|
||||
bootstrapping module in Python 3.4 (along with the upcoming maintenance
|
||||
releases of Python 2.7 and 3.3), as well as changes to the way Python
|
||||
installed scripts are handled on Windows (for Python 3.4 only).
|
||||
releases of Python 2.7 and 3.3), as well as automatic invocation of that
|
||||
module from ``pyvenv`` (for Python 3.4 only), and changes to the way Python
|
||||
installed scripts are handled on Windows (also for Python 3.4 only).
|
||||
|
||||
To clearly demarcate development responsibilities, and to avoid
|
||||
inadvertently downgrading ``pip`` when updating CPython, the proposed
|
||||
|
|
Loading…
Reference in New Issue