[Twisted-Python] A problem with runUntilCurrent

Christopher Armstrong radix at twistedmatrix.com
Mon May 17 10:20:58 EDT 2004

Bill la Forge wrote:

> This means that when you do a callLater with a delay of 0,
> runUntilCurrent will immediately call the delayed function, which then
> calls callLater, and again the delayed function is immediately called, etc.

No, callLater(0,) doesn't call the function synchronously, it calls it 
in the next reactor iteration. i.e., not "*right* now", but "ASAP".

  Twisted | Christopher Armstrong: International Man of Twistery
   Radix  |          Release Manager,  Twisted Project
---------+           http://radix.twistedmatrix.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20040517/3fdcc336/attachment.pgp 

More information about the Twisted-Python mailing list