Tweak how issues are displayed.

Also re-jigger docs in 2.6 for renames to not change all references. This should minimize confusion.
This commit is contained in:
Brett Cannon 2008-05-12 01:27:08 +00:00
parent e784a30c98
commit c28d3347a5
1 changed files with 10 additions and 6 deletions

View File

@ -874,10 +874,15 @@ SimpleXMLRPCServer xmlrpc.server [3]_
Transition Plan Transition Plan
=============== ===============
Issues
-------
Issues related to this PEP: Issues related to this PEP:
* `Issue 2775`_: Master tracking issue * `Issue 2775`_
* `Issue 2828`_: clean up undoc.rst Master tracking issue
* `Issue 2828`_
clean up undoc.rst
.. _Issue 2775: http://bugs.python.org/issue2775 .. _Issue 2775: http://bugs.python.org/issue2775
.. _Issue 2828: http://bugs.python.org/issue2828 .. _Issue 2828: http://bugs.python.org/issue2828
@ -996,14 +1001,13 @@ Python 2.6
#. Update all import statements in the stdlib to use the new name. #. Update all import statements in the stdlib to use the new name.
#. Rename the module in the documentation (both its own and all #. Rename the module in its own documentation.
references).
#. Commit the changes (this checkin should be allowed to propagate to py3k). #. Commit the changes (this checkin should be allowed to propagate to py3k).
#. Add stub entries in the documentation for the old names which #. Add a stub entry in the documentation for the old name which
lists the module as deprecated under that name and points to the lists the module as deprecated under that name and points to the
new name (see the module removal steps on the required steps). new name (see the module removal steps for what is required to do this).
#. In the module's documentation (under the new name), add a #. In the module's documentation (under the new name), add a
``versionchanged`` directive mentioning that the module was ``versionchanged`` directive mentioning that the module was