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 andersk
Recipients amaury.forgeotdarc, andersk, eric.araujo, georg.brandl, pitrou, r.david.murray, rhettinger, ysj.ray
Date 2010-07-22.17:53:30
SpamBayes Score 0.00736777
Marked as misclassified No
Message-id <1279821213.12.0.215611833561.issue8376@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine: That’s true.

Amaury: See my original bug description (“This is reasonable advice for writing an iterator class, but terrible advice for writing a container class…”), and my other comments.

There is nothing wrong with explaining how to write an iterator, but the explanation needs to make clear that this is _not_ how you write a container.  Currently the section opens with a misleading motivation (“By now you have probably noticed that most container objects can be looped over using a for statement”), but it does actually not explain how to write a container at all.  So I proposed some language and an example to fix that.
History
Date User Action Args
2010-07-22 17:53:33andersksetrecipients: + andersk, georg.brandl, rhettinger, amaury.forgeotdarc, pitrou, eric.araujo, r.david.murray, ysj.ray
2010-07-22 17:53:33andersksetmessageid: <1279821213.12.0.215611833561.issue8376@psf.upfronthosting.co.za>
2010-07-22 17:53:31andersklinkissue8376 messages
2010-07-22 17:53:31anderskcreate