RetroSearch Browse

Sun Nov 14 21:05:16 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-November/105601.html

Nick Coghlan <ncoghlan <at> gmail.com> writes:

> of the exception information. logging could also gain an independent
> "stack_trace=True" option to request inclusion of a stack trace
> independently of whether or not exception information is included.

Good point, Nick. There are times when you'd want to know how you got to a
certain point in code, irrespective of whether any exception occurred. So your
suggestion makes sense, and I'll try and see if I can get it into 3.2.

Another benefit of this is that a user only gets this if they want it; if I were
to use the allframes flag in logging, then everyone would get the print_stack()
even if they didn't want it.

Regards,

Vinay Sajip

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-November/105601.html below:

[Python-Dev] unexpected traceback/stack behavior with chained exceptions (issue 1553375)