[Twisted-Python] lost tracebacks?

Jean-Paul Calderone exarkun at divmod.com
Wed Dec 10 18:00:57 EST 2008

On Wed, 10 Dec 2008 22:08:52 -0000, glyph at divmod.com wrote:
>On 08:42 pm, alecf at metaweb.com 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.

There's also Failure.getTracebackObject which returns something that is API
compatible with a real traceback object except that you can't use it with
`raise´.  I'm not sure if it's good enough for Paste's EvalException, though.


More information about the Twisted-Python mailing list