Message214856
Aside from the method being named __next__(), it's the same flaw in all copies of the Py3 documentation.
I don't think explicitly enumerating types is the way to go though. I'd just remove the documentation for __next__, and leave it up to the per-type documentation to describe the data structure returned when iterating. None of the other built-in types in Py3 bother to explicitly document "internal" methods like __next__, but rather describe iteration while describing the type itself. |
|
Date |
User |
Action |
Args |
2014-03-25 21:53:23 | josh.r | set | recipients:
+ josh.r, docs@python, NRGunby |
2014-03-25 21:53:22 | josh.r | set | messageid: <1395784402.96.0.490110761461.issue21056@psf.upfronthosting.co.za> |
2014-03-25 21:53:22 | josh.r | link | issue21056 messages |
2014-03-25 21:53:22 | josh.r | create | |
|