This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author julien.tayon
Recipients docs@python, julien.tayon
Date 2012-12-12.17:39:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355333994.73.0.927546875612.issue16670@psf.upfronthosting.co.za>
In-reply-to
Content
Priority: low
Keywords: documentation

After watching 
http://www.youtube.com/watch?v=o9pEzgHorH0 (Stop writing classes by diedrich)
I think the class Point example for the named tuples may be a wrong practice: 
http://docs.python.org/2/library/collections.html#collections.namedtuple

Since complex basic types

1*  does the same, (if x is real and y is imag)
2*  does more (rotation, norms,  symbolic notation with i)

At my opnion pointing some code to http://bugs.python.org/issue1818 (if it is accepted) may be the case of use of the named tuple.
History
Date User Action Args
2012-12-12 17:39:54julien.tayonsetrecipients: + julien.tayon, docs@python
2012-12-12 17:39:54julien.tayonsetmessageid: <1355333994.73.0.927546875612.issue16670@psf.upfronthosting.co.za>
2012-12-12 17:39:54julien.tayonlinkissue16670 messages
2012-12-12 17:39:54julien.tayoncreate