cpython: transition move technically correct to obviously so

http://hg.python.org/cpython/rev/6af7cb290a24 changeset: 71640:6af7cb290a24 user: Benjamin Peterson <benjamin@python.org> date: Sat Jul 30 12:26:27 2011 -0500 summary: transition move technically correct to obviously so files: Doc/library/stdtypes.rst | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst --- a/Doc/library/stdtypes.rst +++ b/Doc/library/stdtypes.rst @@ -2706,7 +2706,7 @@ This object is returned by functions that don't explicitly return a value. It supports no special operations. There is exactly one null object, named -``None`` (a built-in name). Calling ``type(None)`` produces the same singleton. +``None`` (a built-in name). ``type(None)()`` produces the same singleton. It is written as ``None``. @@ -2718,7 +2718,7 @@ This object is commonly used by slicing (see :ref:`slicings`). It supports no special operations. There is exactly one ellipsis object, named -:const:`Ellipsis` (a built-in name). Calling ``type(Ellipsis)`` produces the +:const:`Ellipsis` (a built-in name). ``type(Ellipsis)()`` produces the :const:`Ellipsis` singleton. It is written as ``Ellipsis`` or ``...``. @@ -2729,8 +2729,8 @@ This object is returned from comparisons and binary operations when they are asked to operate on types they don't support. See :ref:`comparisons` for more -information. There is exactly one ``NotImplemented`` object. Calling -``type(NotImplemented)`` produces the singleton instance. +information. There is exactly one ``NotImplemented`` object. +``type(NotImplemented)()`` produces the singleton instance. It is written as ``NotImplemented``. -- Repository URL: http://hg.python.org/cpython
participants (1)
-
benjamin.peterson