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 Evan Hubinger, josh.r, rhettinger
Date 2015-10-17.05:11:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445058689.75.0.284679060168.issue25429@psf.upfronthosting.co.za>
In-reply-to
Content
This is a duplicate of Issue #14010.  This issue runs deep and isn't itertools specific.  Running infinite chains of iterators pushes a number of CPython internals past their limits.  The best solutions are hard (monitoring the C-stack or fixing every possible fault at the fracture point).  The simplest solution (adding recursion count tracking to every possible iteration)is very heavy-handed and would slow-down all of Python in order to spare exotic cases that don't seem to arise in practice.
History
Date User Action Args
2015-10-17 05:11:29rhettingersetrecipients: + rhettinger, josh.r, Evan Hubinger
2015-10-17 05:11:29rhettingersetmessageid: <1445058689.75.0.284679060168.issue25429@psf.upfronthosting.co.za>
2015-10-17 05:11:29rhettingerlinkissue25429 messages
2015-10-17 05:11:29rhettingercreate