On 07:54 am, gl...@divmod.com wrote:
2. When filing that ticket, I'd really like a full working example of
inlineCallbacks not showing a traceback to play with
Just to drive that point home, Terry, I found an interesting error in
your initial example. Your example does this:
info = s
Hi Glyph
> "glyph" == glyph writes:
glyph> It sounds like the real issue here is that we don't have a channel
glyph> to communicate a "cleaned traceback" (i.e., failure with stringified
glyph> frames, but no traceback) from one bit of code to another?
Yes, now that I better understand what'
> "glyph" == glyph writes:
glyph> Just to drive that point home, Terry, I found an interesting error
glyph> in your initial example. Your example does this:
glyph> info = sys.exc_info()
glyph> f = failure.Failure(*info)
glyph> but sys.exc_info() is a tuple of (type, value, traceback), whe
Hi all.
> "glyph" == glyph writes:
glyph> 1. More of this discussion should be on a ticket.
See http://twistedmatrix.com/trac/ticket/3622
Terry
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mai
Bug summary
__
Summary for 2009-01-11 through 2009-01-18
Bugs opened: 9Bugs closed: 18 Total open bugs: 1040 (-9)
|== Type Changes |== Priority Changes |== Component Changes
|Defect: -4 |Highest: -1 |Core: -1
|Enhancement: -5 |Hi
