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 Rosuav
Recipients Rosuav, gvanrossum, python-dev, schlamar
Date 2014-11-21.17:44:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yep, the question is whether any of the "raise StopIteration" lines are actually non-local flow control. If they're local, then it's easy: mechanical replacement with "return" and it becomes compatible with all versions (unless it has a value attached to it, as "return x" doesn't work in Py2). But if they're non-local, some refactoring will need to be done.

In any case, my line of argument is: A generator function is not an iterator's __next__ method, ergo iterator protocol does not apply. Use of StopIteration is a hack that happens to work because of how generator functions are implemented (a thin wrapper around an iterator), but it's not part of the *concept* of a generator function.
Date User Action Args
2014-11-21 17:44:46Rosuavsetrecipients: + Rosuav, gvanrossum, python-dev, schlamar
2014-11-21 17:44:46Rosuavsetmessageid: <>
2014-11-21 17:44:46Rosuavlinkissue22906 messages
2014-11-21 17:44:45Rosuavcreate