On Sun, 2008-01-13 at 19:06 +0100, Tanja wrote:
> It seems that error messages are silently dropped when the error occures in
> the decorated function.
> Where are those messages going? Is it possible to make this more verbose? It
> is very irritating to
> debug without any output from the crash...
This may be something specific to freevo 1.x that Duncan can comment on.
Because by default the exception does get logged.
In fact, it gets logged twice when there is no callback connected to
exception_handler. Dischi, should we suppress the log.exception in
yieldfunc.py:229 and leave it to async.py:163? This way properly
handled exceptions don't get logged.
Consider this test:
import kaa
@kaa.yield_execution()
def func():
for i in range(10):
print i
if i == 9:
raise ValueError, "test"
yield kaa.YieldContinue
func()
kaa.main.run()
This does log the exception. (Twice, as I said.)
2008-01-13 13:53:32,344 [ERROR] __init__(1021): YieldFunction
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/kaa/notifier/yieldfunc.py",
line 223, in _step
result = self._yield__function()
File "not.py", line 8, in func
raise ValueError, "test"
ValueError: test
2008-01-13 13:53:32,345 [ERROR] async(163): *** InProgress exception
not handled ***
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/kaa/notifier/yieldfunc.py",
line 223, in _step
result = self._yield__function()
File "not.py", line 8, in func
raise ValueError, "test"
ValueError: test
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
