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
Date 2010-08-02.04:03:01
SpamBayes Score 0.00613271
Marked as misclassified No
Message-id <1280721783.5.0.811759792933.issue1553375@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a proof of concept patch that adds a 'fullstack' option to print_exception.  The problem with this concept is what happens when you use it on an exception caught at the top level of a module.  I'm not entirely clear on why tracebacks work the way they do, so I don't know how to fix that case (it's also late, maybe in the morning I'll be able to figure it out :)

Writing unit tests for this may also be a bit tricky.

I'm raising the priority to normal because I think this would be really useful for logging, as pointed out by Thomas.
History
Date User Action Args
2010-08-02 04:03:03r.david.murraysetrecipients: + r.david.murray, guettli, hoffman, ggenellina, pakal, news1234
2010-08-02 04:03:03r.david.murraysetmessageid: <1280721783.5.0.811759792933.issue1553375@psf.upfronthosting.co.za>
2010-08-02 04:03:02r.david.murraylinkissue1553375 messages
2010-08-02 04:03:01r.david.murraycreate