[Python-checkins] r71599 - python/branches/py3k/Doc/whatsnew/3.1.rst

[raymond.hettinger]

Author: raymond.hettinger
Date: Tue Apr 14 10:16:50 2009
New Revision: 71599

Log:
Fix-up links.

Modified:
   python/branches/py3k/Doc/whatsnew/3.1.rst

Modified: python/branches/py3k/Doc/whatsnew/3.1.rst
==============================================================================
--- python/branches/py3k/Doc/whatsnew/3.1.rst	(original)
+++ python/branches/py3k/Doc/whatsnew/3.1.rst	Tue Apr 14 10:16:50 2009
@@ -57,8 +57,8 @@
 Regular Python dictionaries iterate over key/value pairs in arbitrary order.
 Over the years, a number of authors have written alternative implementations
 that remember the order that the keys were originally inserted.  Based on
-the experiences from those implementations, the :mod:`collections` module
-now has an :class:`OrderedDict` class.
+the experiences from those implementations, a new
+:class:`collections.OrderedDict` class has been introduced.
 
 The OrderedDict API is substantially the same as regular dictionaries
 but will iterate over keys and values in a guaranteed order depending on
@@ -69,7 +69,7 @@
 The standard library now supports use of ordered dictionaries in several
 modules.  The :mod:`configparser` module uses them by default.  This lets
 configuration files be read, modified, and then written back in their original
-order.  The :mod:`collections` module's :meth:`namedtuple._asdict` method now
+order.  The *_asdict()* method for :func:`collections.namedtuple` now
 returns an ordered dictionary with the values appearing in the same order as
 the underlying tuple indicies.  The :mod:`json` module is being built-out with
 an *object_pairs_hook* to allow OrderedDicts to be built by the decoder.
@@ -233,15 +233,15 @@
 
   (Contributed by Gregory Smith.)
 
-* The :mod:`logging` module now implements a simple :class:`NullHandler`
+* The :mod:`logging` module now implements a simple :class:`logging.NullHandler`
   class for applications that are not using logging but are calling
   library code that does.  Setting-up a null handler will suppress
-  spurious warnings like "No handlers could be found for logger X.Y.Z"::
+  spurious warnings such as "No handlers could be found for logger foo"::
 
     >>> h = logging.NullHandler()
     >>> logging.getLogger("foo").addHandler(h)
 
-  (Contributed by Vinay Sajip; issue:`4384`).
+  (Contributed by Vinay Sajip; :issue:`4384`).
 
 * The :mod:`runpy` module which supports the ``-m`` command line switch
   now supports the execution of packages by looking for and executing