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 pitrou
Recipients ezio.melotti, kristjan.jonsson, meador.inge, pitrou, progrper, rhettinger, terry.reedy
Date 2012-04-15.17:07:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334509616.3414.6.camel@localhost.localdomain>
In-reply-to <1334508463.42.0.863490989266.issue14507@psf.upfronthosting.co.za>
Content
> The existing sys.max_recursion_depth was put in as a defense against
> the relatively common mistake of users writing a recursive function
> and getting the termination code wrong.   I don't think that logic
> would apply to intentionally deeply nested data structures or
> iterators.

Well, we have a history of trying to fix crashers, even when they only
occur in weird cases.

> Stackoverflows in C are hard to protect against.

We could simply re-use the existing infrastructure.
History
Date User Action Args
2012-04-15 17:07:51pitrousetrecipients: + pitrou, rhettinger, terry.reedy, kristjan.jonsson, ezio.melotti, meador.inge, progrper
2012-04-15 17:07:50pitroulinkissue14507 messages
2012-04-15 17:07:50pitroucreate