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 ncoghlan, rhettinger
Date 2018-06-22.12:48:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529671694.59.0.56676864532.issue33939@psf.upfronthosting.co.za>
In-reply-to
Content
This is a simpler proposal born out of https://bugs.python.org/issue31815: adding __length_hint__ implementations to some known-infinite iterators in itertools that always raise TypeError.

This means that iterator consumers that use the operator.length_hint() API will throw an error when asked to consume them, rather than entering an uninterruptible infinite loop.

The proposed methods added by this proposal would be:

* itertools.count.__length_hint__
* itertools.cycle.__length_hint__
* itertools.repeat.__length_hint__

Each of these would raise TypeError (to indicate an explicitly non-finite length), rather than returning the default of 0 (which length hint API consumers typically interpret as indicating an unknown-but-finite length)
History
Date User Action Args
2018-06-22 12:48:14ncoghlansetrecipients: + ncoghlan, rhettinger
2018-06-22 12:48:14ncoghlansetmessageid: <1529671694.59.0.56676864532.issue33939@psf.upfronthosting.co.za>
2018-06-22 12:48:14ncoghlanlinkissue33939 messages
2018-06-22 12:48:14ncoghlancreate