Update PEP453 to address Debian's concerns and Antoine's
This commit is contained in:
parent
28b3bbec03
commit
49665d3360
10
pep-0453.txt
10
pep-0453.txt
|
@ -294,7 +294,9 @@ command with the just installed Python::
|
|||
|
||||
This ensures that, by default, installing or updating CPython will ensure
|
||||
that the installed version of pip is at least as recent as the one included
|
||||
with that version of CPython.
|
||||
with that version of CPython. If a newer version of pip has already been
|
||||
installed then ``python -m extractpip --upgrade`` will simply return without
|
||||
doing anything.
|
||||
|
||||
|
||||
Installing from source
|
||||
|
@ -532,6 +534,12 @@ downstream distributors:
|
|||
* This may take the form of separate packages with dependencies on each
|
||||
other so that installing the Python package installs the pip package
|
||||
and installing the pip package installs the Python package.
|
||||
* Another reasonable way to implement this is to package pip separately but
|
||||
ensure that there is some sort of global hook that will recommend
|
||||
installing the separate pip package when a user executes ``pip`` without
|
||||
it being installed. Systems that choose this option should ensure that
|
||||
the ``pyvenv`` command still installs pip into the virtual environment
|
||||
by default.
|
||||
|
||||
* Do not remove the bundled copy of pip.
|
||||
|
||||
|
|
Loading…
Reference in New Issue