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 rhettinger
Recipients ncoghlan, rhettinger, serhiy.storchaka
Date 2017-10-18.17:34:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508348087.96.0.213398074469.issue31815@psf.upfronthosting.co.za>
In-reply-to
Content
When I have time, I would like to re-launch a python-dev discussion on this.  It is my feeling that this solves an invented problem.  In my experience, it only ever happens to people who have intentionally trying to create this effect.

Adding this kind of "junk" through-out the code base adds complexity and more internal operations, but won't help *any* existing, deployed code.  We're making everyone pay for a problem that almost no one has.

Also, if we do care about interruptability, it is unclear whether the responsiblity should like with the consumer or the producer of the iterator.
History
Date User Action Args
2017-10-18 17:34:47rhettingersetrecipients: + rhettinger, ncoghlan, serhiy.storchaka
2017-10-18 17:34:47rhettingersetmessageid: <1508348087.96.0.213398074469.issue31815@psf.upfronthosting.co.za>
2017-10-18 17:34:47rhettingerlinkissue31815 messages
2017-10-18 17:34:47rhettingercreate