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 hoffman
Recipients
Date 2006-09-06.12:48:54
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
The suggestion is to add something roughly like this:

def print_full_exception(type, value, traceback, file):
.   _print(sys.stderr, 'Traceback (most recent call
last):')
.   print_stack(traceback.tb_frame.f_back, file=file)
.   print_tb(traceback, file=file)
.
.   lines = format_exception_only(type, value)
.   for line in lines[:-1]:
.       _print(file, line, ' ')
.   _print(file, lines[-1], '')


to the traceback module, to print the exception not
just downward from the calling point, but also upward
all the way to the top of the stack. This would be
useful in, e.g. logging, where exceptions are caught
and printed, but right now no information is given as
to where they occurred in user code.
History
Date User Action Args
2008-01-20 09:59:50adminlinkissue1553375 messages
2008-01-20 09:59:50admincreate