Sept. 30, 2010
3:45 a.m.
On 12:52 am, chris@simplistix.co.uk wrote:
Because I haven't found any permutation that doesn't result in the LoopingCall's calls to `loop` from stopping after the exception.
I would be more than ecstatic to be proved wrong ;-)
You keep saying the LoopingCall stops. It does not stop. It is waiting for a result. If you provide it with a result, it will proceed. Glyph suggested a number of (hackfully) mechanisms you might use to provide it with a result. I suggested another way (fix the broken code, or at least supply enough information for someone else to fix it). Jean-Paul