[Python-checkins] r69955 - python/trunk/Doc/library/functions.rst
python-checkins at python.org
Wed Feb 25 01:52:37 CET 2009
Date: Wed Feb 25 01:52:37 2009
New Revision: 69955
More markup and spelling fixes.
--- python/trunk/Doc/library/functions.rst (original)
+++ python/trunk/Doc/library/functions.rst Wed Feb 25 01:52:37 2009
@@ -1198,9 +1198,9 @@
been overridden in a class. The search order is same as that used by
:func:`getattr` except that the *type* itself is skipped.
- The ``__mro__`` attribute of the *type* lists the method resolution search
- order used by both :func:`getattr` and :func:`super`. The attribue is
- dynamic and can change whenever the inheritance hierarchy is updated.
+ The :attr:`__mro__` attribute of the *type* lists the method resolution
+ search order used by both :func:`getattr` and :func:`super`. The attribute
+ is dynamic and can change whenever the inheritance hierarchy is updated.
If the second argument is omitted, the super object returned is unbound. If
the second argument is an object, ``isinstance(obj, type)`` must be true. If
@@ -1210,10 +1210,10 @@
:func:`super` only works for :term:`new-style class`\es.
- There are two typical use cases for "super". In a class hierarchy with
- single inheritance, "super" can be used to refer to parent classes without
+ There are two typical use cases for *super*. In a class hierarchy with
+ single inheritance, *super* can be used to refer to parent classes without
naming them explicitly, thus making the code more maintainable. This use
- closely parallels the use of "super" in other programming languages.
+ closely parallels the use of *super* in other programming languages.
The second use case is to support cooperative multiple inheritance in a
dynamic execution environment. This use case is unique to Python and is
More information about the Python-checkins