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 alex, amaury.forgeotdarc, arigo, benjamin.peterson, ezio.melotti, python-dev, rhettinger, serhiy.storchaka
Date 2013-04-06.19:31:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365276669.14.0.024173901512.issue14010@psf.upfronthosting.co.za>
In-reply-to
Content
I would appreciate it if you would please revert this patch.  

We need to search for a solution that isn't as fine grained (i.e. not doing increments, decrements, and tests on every single call to iter_next).  Ideally, the checks can be confined to the iterator constructor and to dealloc.  Or you could try to create some general purpose stack overflow protection that periodically makes sure there is enough stack remaining for C Python to function correctly.
History
Date User Action Args
2013-04-06 19:31:09rhettingersetrecipients: + rhettinger, arigo, amaury.forgeotdarc, benjamin.peterson, ezio.melotti, alex, python-dev, serhiy.storchaka
2013-04-06 19:31:09rhettingersetmessageid: <1365276669.14.0.024173901512.issue14010@psf.upfronthosting.co.za>
2013-04-06 19:31:09rhettingerlinkissue14010 messages
2013-04-06 19:31:08rhettingercreate