Opened 10 years ago

Closed 7 years ago

Last modified 7 years ago

#4659 enhancement closed duplicate (duplicate)

twisted.web._newclient._WrapperException makes it a little tedious to debug

Reported by: Drew Smathers Owned by:
Priority: low Milestone:
Component: web Keywords:
Cc: Branch:

Description (last modified by Glyph)

Getting a traceback (e.g. reason.printTraceback) with _WrapperException leads to something inscrutable. Example:

Unhandled Error
        Traceback (most recent call last):
        Failure: twisted.web._newclient.RequestGenerationFailed: [<twisted.python.failure.Failure <type 'exceptions.AttributeError'>>]

I don't know if it's possible but it would be nice to somehow get a meaningful traceback without having to introspect the exception type and doing stuff like:

for reason in reason.value.reasons:

Change History (5)

comment:1 Changed 9 years ago by <automation>

Owner: Jean-Paul Calderone deleted

comment:2 Changed 9 years ago by Glyph

Description: modified (diff)

(fixing formatting)

comment:3 Changed 9 years ago by Glyph

#5345 is related to this.

comment:4 Changed 7 years ago by therve

Resolution: duplicate
Status: newclosed

comment:5 Changed 7 years ago by therve

Closed in favor of #5310.

Note: See TracTickets for help on using tickets.