[Twisted-Python] callLater(0) is A BIG LIE

Stefan Behnel behnel_ml at gkec.informatik.tu-darmstadt.de
Tue Nov 2 04:04:03 EST 2004

Bob Ippolito schrieb:
> Actually callLater(0, ....) was an edge case up until recently (I hope 
> it got fixed?) where it DID run in the current iteration.. a timer that 
> fired another timer with 0 delay would cause the timer processing to 
> never finish, so IO wouldn't happen anymore.

I assume that my patch which includes a fix for the bug you mentioned and 
which was supposed to fix the more general performance issues of the 
ReactorTime implementation, is still hanging in the bug-tracker.


More information about the Twisted-Python mailing list