➜

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 orsenthil
Recipients catlee, davide.rizzo, eric.araujo, georg.brandl, jhylton, orsenthil, pitrou, rcoyner, rhettinger, xuanji
Date 2010-12-02.02:23:18
SpamBayes Score 0.00033365103
Marked as misclassified No
Message-id <20101202022312.GB1873@rubuntu>
In-reply-to <1291215416.28.0.0920358124785.issue3243@psf.upfronthosting.co.za>
Content 
On Wed, Dec 01, 2010 at 02:56:56PM +0000, Xuanji Li wrote:
> orsenthil: Hi, i don't quite understand why iter() needs to be
> called explicitly on data? As I understand it, if data is an
> iterable then you can use a for loop on it directly.
> 

The reasoning I followed was, data is an "Iterable" (a collection) and
you get an "Iterator" by passing via iter(). And you send the items by
looping over the iterator.

Honestly, I am not sure if iter is needed here too. I thought it was
not needed too, when you determine it is an Iterable and iterate over
it using the for loop. But I kept the iter() method just to create an
instance and send it.

Antoine, which would be the correct/ better?
History
Date User Action Args
2010-12-02 02:23:20orsenthilsetrecipients: + orsenthil, jhylton, georg.brandl, rhettinger, pitrou, catlee, eric.araujo, rcoyner, xuanji, davide.rizzo
2010-12-02 02:23:19orsenthillinkissue3243 messages
2010-12-02 02:23:18orsenthilcreate