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 anthony-flury
Recipients anthony-flury, bbayles, berker.peksag, eric.araujo, ezio.melotti, michael.foord, ned.deily, rbcollins
Date 2018-07-09.17:04:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531155841.58.0.56676864532.issue32933@psf.upfronthosting.co.za>
In-reply-to
Content
But the __next__ is a method on the iterator; 

So long as __iter__ returns a valid iterator (which it does in my pull request), it will by definition support __next___

Although it is entirely possible that I have misunderstood what you are saying.
History
Date User Action Args
2018-07-09 17:04:01anthony-flurysetrecipients: + anthony-flury, rbcollins, ned.deily, ezio.melotti, eric.araujo, michael.foord, berker.peksag, bbayles
2018-07-09 17:04:01anthony-flurysetmessageid: <1531155841.58.0.56676864532.issue32933@psf.upfronthosting.co.za>
2018-07-09 17:04:01anthony-flurylinkissue32933 messages
2018-07-09 17:04:01anthony-flurycreate