On 07/16/2015 04:00 PM, Chris Angelico wrote: > On Thu, Jul 16, 2015 at 11:56 PM, Antoon Pardon > <antoon.par...@rece.vub.ac.be> wrote: >> Fine, I should have been more clear. >> >> The stack trace as it is generally produced on stderr after an uncought >> exception, doesn't contain the values of the variables on the stack. > Sure. So you catch it at top level and grab whatever info you need. In > some frameworks, this is already done for you - an uncaught exception > from application code drops you into a debugger that lets you explore > and even execute code at any level in the stack.
What is unclear about "as it is generally produced on stderr"? That you can do a whole lot of stuff, doesn't mean that this whole lot of stuff is part of what generally happens. When people on this list ask a person to include the stacktrace with the description of the problem, they don't mean something that includes the values of the variables. -- https://mail.python.org/mailman/listinfo/python-list
