iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

More PEP 453 cleanups

This commit is contained in:
Nick Coghlan 2013-09-29 17:02:03 +10:00
parent d4fc58c7e7
commit 6482692ff6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0453.txt
View File

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