Re-arrange the commit order to minimize commits.
This commit is contained in:
parent
c6f94dc99d
commit
e2698404a7
26
pep-3108.txt
26
pep-3108.txt
|
@ -958,6 +958,13 @@ example of how to approach this.
|
|||
Python 2.6
|
||||
//////////
|
||||
|
||||
#. Update all import statements in the stdlib to use the new name.
|
||||
|
||||
#. Rename the module in the documentation (both its own and all
|
||||
references).
|
||||
|
||||
#. Commit the changes (this checkin should be allowed to propagate to py3k).
|
||||
|
||||
#. Use ``svn move`` to rename the module.
|
||||
|
||||
#. Create a stub module in ``Lib/lib-old``::
|
||||
|
@ -972,23 +979,18 @@ Python 2.6
|
|||
|
||||
#. Add a test to ``test_py3kwarn``.
|
||||
|
||||
#. Add a ``warning`` directive to the module's documentation.
|
||||
#. Add stub entries in the documentation for the old names which
|
||||
lists the module as deprecated under that name and points to the
|
||||
new name (see the module removal steps on the required steps).
|
||||
|
||||
#. In the module's documentation (under the new name), add a
|
||||
``versionchanged`` directive mentioning that the module was
|
||||
renamed in Python 2.6.
|
||||
|
||||
#. Add an entry in ``Misc/NEWS``.
|
||||
|
||||
#. Commit the changes (**block** in py3k).
|
||||
|
||||
#. Update all import statements in the stdlib to use the new name.
|
||||
|
||||
#. Rename the module in the documentation (both its own and all
|
||||
references).
|
||||
|
||||
#. Commit the changes (this checkin should be allowed to propagate to py3k).
|
||||
|
||||
#. Add stub entries in the documentation for the old names which
|
||||
lists the module as deprecated under that name and points to the
|
||||
new name (see the module removal steps on the required steps).
|
||||
|
||||
|
||||
Python 3.0
|
||||
//////////
|
||||
|
|
Loading…
Reference in New Issue