On 08:42 pm, [EMAIL PROTECTED] wrote:
I was hoping for a "real" traceback because Paste's EvalException middleware does a nice job debugging "live" stacks, but the 'verbose' stack is a pretty decent stand-in.
There's a good reason not to hang on to the "real" traceback. Failures with verbose stacktraces can already take up a shocking amount of memory (as you can see on this ticket: <http://twistedmatrix.com/trac/ticket/2466>). Actually keeping around *all* of the original stack frames means keeping a live reference to everything that was on the stack at the time the error happened, which can potentially be the entire world.
_______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
