On Fri, 23 Jan 2009 13:17:32 -0500, Kangkook Jee <aixe...@gmail.com> wrote:
Hi all
I'm a Twisted newbie and I have a question about exception handling of
Twisted framework.
Whenever I got some exception raised from somewhere, I got truncated
exception message like this.
>>>Traceback (most recent call last):
File "./fcli.py", line 68, in <module>
reactor.run()
File "/opt/local/lib/python2.5/site-packages/twisted/internet/
posixbase.py", line 223, in run
self.mainLoop()
File "/opt/local/lib/python2.5/site-packages/twisted/internet/
posixbase.py", line 234, in mainLoop
self.doIteration(t)
File "/opt/local/lib/python2.5/site-packages/twisted/internet/
selectreactor.py", line 140, in doSelect
_logrun(selectable, _drdw, selectable, method, dict)
--- <exception caught here> ---
File "/opt/local/lib/python2.5/site-packages/twisted/python/ log.py", line
51, in callWithLogger
return callWithContext({"system": lp}, func, *args, **kw)
File "/opt/local/lib/python2.5/site-packages/twisted/python/ log.py", line
36, in callWithContext
return context.call({ILogContext: newCtx}, func, *args, **kw)
File "/opt/local/lib/python2.5/site-packages/twisted/python/ context.py",
line 59, in callWithContext
return self.currentContext().callWithContext(ctx
and this make me so hard to find exact cause of the problem.
Can anyone tell me how can I solve this problem?
This isn't the usual behavior of the exception reporting code in Twisted.
Normally the entire traceback and exception are reported. Can you post a
minimal example which reproduces this behavior?
Jean-Paul
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
