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 rbcollins
Recipients chris.jerdonek, ezio.melotti, michael.foord, rbcollins
Date 2016-03-16.18:35:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458153316.96.0.413679142136.issue24959@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, it is... ish.

The frame skipping code occurs when we serialise exceptions, and we pass a limit in. The limit is calculated on the main exception only. If the cause has a longer exception than the limit we calculated, you'd see this behaviour.

Probably need to make it possible to do per-exception processing of limit: I think via a callback or similar mechanism in traceback (because the cause might have thrown from some code that is also marked __unittest, so if we're honouring that, we should honour it within each exception.
History
Date User Action Args
2016-03-16 18:35:17rbcollinssetrecipients: + rbcollins, ezio.melotti, michael.foord, chris.jerdonek
2016-03-16 18:35:16rbcollinssetmessageid: <1458153316.96.0.413679142136.issue24959@psf.upfronthosting.co.za>
2016-03-16 18:35:16rbcollinslinkissue24959 messages
2016-03-16 18:35:16rbcollinscreate