➜

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 dino.viehland
Recipients Emmanuel.Decitre, Peter.Wentworth, asvetlov, dino.viehland, flupke, gregorlingl, kbk, loewis, pitrou, r.david.murray, terry.reedy
Date 2012-04-12.16:25:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334247916.85.0.267497352776.issue6717@psf.upfronthosting.co.za>
In-reply-to
Content 
It's catching the exception when it invokes x, but the recursion enforcement should happen at a method prolog, including at the invocation of g.  Therefore if we're at or beyond the recursion limit when invoking the trace handler the limits should still be enforced and that should be the same as the trace handler raising.
History
Date User Action Args
2012-04-12 16:25:16dino.viehlandsetrecipients: + dino.viehland, loewis, terry.reedy, kbk, pitrou, gregorlingl, r.david.murray, asvetlov, flupke, Peter.Wentworth, Emmanuel.Decitre
2012-04-12 16:25:16dino.viehlandsetmessageid: <1334247916.85.0.267497352776.issue6717@psf.upfronthosting.co.za>
2012-04-12 16:25:16dino.viehlandlinkissue6717 messages
2012-04-12 16:25:16dino.viehlandcreate