[issue16670] [docs] class Point in collections.namedtuples may be not that good example

[julien tayon]

New submission from julien tayon:

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.

--
assignee: docs@python
components: Documentation
messages: 177382
nosy: docs@python, julien.tayon
priority: normal
severity: normal
status: open
title: [docs] class Point in collections.namedtuples may be not that good 
example
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16670
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16670] [docs] class Point in collections.namedtuples may be not that good example

[Raymond Hettinger]

Raymond Hettinger added the comment:

I like the current example.  It does a great job teaching people how 
namedtuples work.  Also, I think you've drawn the wrong conclusions from Jack's 
talk.

--
assignee: docs@python - rhettinger
nosy: +jackdied, rhettinger
priority: normal - low

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16670
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com