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 r.david.murray
Recipients ggenellina, guettli, hoffman, news1234, pakal, r.david.murray, ysj.ray
Date 2010-08-04.02:32:57
SpamBayes Score 4.974003e-09
Marked as misclassified No
Message-id <1280889182.53.0.800988810141.issue1553375@psf.upfronthosting.co.za>
In-reply-to
Content
Updated patch with unit tests and docs.  I realized that I'd forgotten to test chained exceptions.  It looks like when the Interpreter prints a traceback all the exceptions in the chain are printed fully, which makes sense.  Adopting that strategy for this patch simplified it into three lines (the signature change and an if/print in the loop).

I'm pretty satisfied with this patch.  I have two questions: should the 'fullstack' option really be implemented in print_tb instead?  And is there a better name for the option?  Would just 'full' be acceptable?
History
Date User Action Args
2010-08-04 02:33:03r.david.murraysetrecipients: + r.david.murray, guettli, hoffman, ggenellina, pakal, news1234, ysj.ray
2010-08-04 02:33:02r.david.murraysetmessageid: <1280889182.53.0.800988810141.issue1553375@psf.upfronthosting.co.za>
2010-08-04 02:33:00r.david.murraylinkissue1553375 messages
2010-08-04 02:33:00r.david.murraycreate