Tweak the proposed integration timeline
This commit is contained in:
parent
92d4dbf0ec
commit
9fba6aeaad
43
pep-0453.txt
43
pep-0453.txt
|
@ -405,36 +405,47 @@ can be carried out in any order):
|
|||
Integration timeline
|
||||
--------------------
|
||||
|
||||
Allowing ``pip`` to be bundled with CPython as a wheel file requires some
|
||||
adjustments to ``pip`` itself, so the proposed time frame for integration
|
||||
into CPython if this PEP is accepted is as follows:
|
||||
If this PEP is accepted, the proposed time frame for integration of ``pip``
|
||||
into the CPython release is as follows:
|
||||
|
||||
* by November 17th (1 week prior to the scheduled date of 3.4.0 beta 1)
|
||||
* as soon as possible
|
||||
|
||||
Documentation updated and ``ensurepip`` implemented based on a beta release
|
||||
of ``pip`` 1.5.
|
||||
Documentation updated and ``ensurepip`` implemented based on a pre-release
|
||||
version of ``pip`` 1.5.
|
||||
|
||||
All other proposed functional changes for Python 3.4 implemented,
|
||||
including the installer updates to invoke ``ensurepip``.
|
||||
|
||||
* by November 20th (3 days prior to the scheduled date of 3.4.0 beta 1)
|
||||
|
||||
``ensurepip`` updated to use a beta release of ``pip`` 1.5.
|
||||
|
||||
PEP 101 updated to cover ensuring the bundled version of ``pip`` is up
|
||||
to date.
|
||||
|
||||
* by November 24th (scheduled date of 3.4.0 beta 1)
|
||||
|
||||
All other proposed functional changes for Python 3.4 implemented,
|
||||
including the installer updates to invoke ensurepip.
|
||||
As with any other new feature, all proposed functional changes for
|
||||
Python 3.4 must be implemented prior to the beta feature freeze.
|
||||
|
||||
* by December 29th (1 week prior to the scheduled date of 3.4.0 beta 2)
|
||||
|
||||
``ensurepip`` updated to the final release of pip 1.5
|
||||
|
||||
PEP 101 updated to cover ensuring the bundled version of ``pip`` is up
|
||||
to date.
|
||||
|
||||
(See PEP 429 for the current official scheduled dates of each release. Dates
|
||||
listed above are accurate as of October 15th.)
|
||||
|
||||
If there is no final release of ``pip`` 1.5 available the week before the
|
||||
If there is no final release of ``pip`` 1.5 available by one week before the
|
||||
scheduled Python 3.4 beta 2 release, then implementation of this PEP will
|
||||
be deferred to Python 3.5. Note that this scenario is unlikely - the final
|
||||
``pip`` 1.5 release could likely be ready for beta 1. However, it makes
|
||||
sense to defer the final release until after the ``ensurepip`` bootstrapping
|
||||
has seen some testing in a CPython beta release.
|
||||
be deferred to Python 3.5. Note that this scenario is unlikely - the
|
||||
tentative date for the ``pip`` 1.5 release is currently December 1st.
|
||||
|
||||
In future CPython releases, this kind of coordinated scheduling shouldn't be
|
||||
needed: the CPython release manager will be able to just update to the latest
|
||||
released version of ``pip``. However, in this case, some fixes are needed in
|
||||
``pip`` in order to allow the bundling to work correctly, so the ``pip`` 1.5
|
||||
release cycle needs to be properly aligned with the CPython 3.4 beta
|
||||
releases.
|
||||
|
||||
|
||||
Proposed CLI
|
||||
|
|
Loading…
Reference in New Issue