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 ncoghlan
Recipients koos.zevenhoven, ncoghlan, rhettinger, serhiy.storchaka
Date 2017-10-19.07:50:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508399458.93.0.213398074469.issue31815@psf.upfronthosting.co.za>
In-reply-to
Content
I'd personally be happy enough if the infinite iterators implemented __length_hint__() as always raising TypeError so the machine-breaking cases of incremental consumption of ever-increasing amounts of memory were blocked - I was suggesting on python-ideas that enabling pervasive signal checking would be too intrusive for anyone to be willing to implement it.

However, Serhiy's patch showed me that it isn't particularly intrusive at all, and the risk of surprising consumers is low, since __next__() methods can already raise arbitrary exceptions.
History
Date User Action Args
2017-10-19 07:50:58ncoghlansetrecipients: + ncoghlan, rhettinger, serhiy.storchaka, koos.zevenhoven
2017-10-19 07:50:58ncoghlansetmessageid: <1508399458.93.0.213398074469.issue31815@psf.upfronthosting.co.za>
2017-10-19 07:50:58ncoghlanlinkissue31815 messages
2017-10-19 07:50:58ncoghlancreate