On 2008-01-11 12:31, Jason Tackaberry wrote: > BTW I just had a thought: perhaps we should have a > kaa.signals['exception'] signal, which gets called when any unhandled > exception bubbles up to the notifier level. Because we're no better > than twisted here, by just dumping the exception and carrying no, giving > the user no way to handle it.
Well I guess we do have a way to handle it, by wrapping kaa.main.start() in a try/except clause. It'd be nicer to have a global exception signal that if there is a handler connected to it, we won't stop the main loop, but will rather just invoke the handler and continue (giving the handler the option to shutdown or not). ------------------------------------------------------------------------- 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
