From: Raymond Hettinger Date: Sun, 27 Jan 2008 10:47:55 +0000 (+0000) Subject: Removed an unnecessary and confusing paragraph from the namedtuple docs. X-Git-Tag: v2.6a1~373 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9bba7b70852bc0aff6abafcafe46c25c19eb8f81;p=python Removed an unnecessary and confusing paragraph from the namedtuple docs. --- diff --git a/Doc/library/collections.rst b/Doc/library/collections.rst index a891aff869..58449fe843 100644 --- a/Doc/library/collections.rst +++ b/Doc/library/collections.rst @@ -526,16 +526,7 @@ a fixed-width print format:: Point: x= 3.000 y= 4.000 hypot= 5.000 Point: x=14.000 y= 0.714 hypot=14.018 -Another use for subclassing is to replace performance critcal methods with -faster versions that bypass error-checking:: - - class Point(namedtuple('Point', 'x y')): - __slots__ = () - _make = classmethod(tuple.__new__) - def _replace(self, _map=map, **kwds): - return self._make(_map(kwds.get, ('x', 'y'), self)) - -The subclasses shown above set ``__slots__`` to an empty tuple. This keeps +The subclass shown above sets ``__slots__`` to an empty tuple. This keeps keep memory requirements low by preventing the creation of instance dictionaries. Subclassing is not useful for adding new, stored fields. Instead, simply