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 terry.reedy
Recipients Zero, docs@python, r.david.murray, terry.reedy
Date 2013-07-26.23:28:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374881300.41.0.724065168772.issue18558@psf.upfronthosting.co.za>
In-reply-to
Content
Stephen, your class, or rather instances thereof when initialized with a sequence, follow the old iteration protocol. You might call them iterators in the generic sense, though I cannot remember whether we used 'iterator' much before the introduction of the new and now dominant iteration protocol. I am sure 'iterable' was introduced with the new protocol for objects with .__iter__ methods that return iterators, which in this context means an object with a .__next__ method and excludes .__getitem__ objects.

It would have been less confusing is we had disabled the old protocol in 3.0, but aside from the predictable confusion, it seemed better to keep it.
History
Date User Action Args
2013-07-26 23:28:20terry.reedysetrecipients: + terry.reedy, r.david.murray, Zero, docs@python
2013-07-26 23:28:20terry.reedysetmessageid: <1374881300.41.0.724065168772.issue18558@psf.upfronthosting.co.za>
2013-07-26 23:28:20terry.reedylinkissue18558 messages
2013-07-26 23:28:20terry.reedycreate