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 vinay.sajip
Recipients guettli, vinay.sajip
Date 2010-08-26.13:31:59
SpamBayes Score 2.3100306e-07
Marked as misclassified No
Message-id <1282829521.29.0.699525590194.issue9427@psf.upfronthosting.co.za>
In-reply-to
Content
This also happens on later versions. Since 2.x is essentially frozen, this feature request can't be implemented in 2.x, so recategorising as a Python 3.2 issue.

Here, a change in logging will either duplicate code in traceback.py or print the upper frames above the "Traceback (most recent call last):" line, which is not ideal.

The best way to implement in logging would be to wait for the implementation of the patch in #1553375, following which a change could be made in Formatter.formatException to invoke traceback.print_exception with the "fullstack" keyword parameter.
History
Date User Action Args
2010-08-26 13:32:01vinay.sajipsetrecipients: + vinay.sajip, guettli
2010-08-26 13:32:01vinay.sajipsetmessageid: <1282829521.29.0.699525590194.issue9427@psf.upfronthosting.co.za>
2010-08-26 13:31:59vinay.sajiplinkissue9427 messages
2010-08-26 13:31:59vinay.sajipcreate