[Twisted-Python] A problem with runUntilCurrent
Itamar Shtull-Trauring
itamar at itamarst.org
Mon May 17 08:22:52 MDT 2004
On Mon, 2004-05-17 at 10:14, 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.
And that's why testImmediateThread failed. Attached is a fixed up patch
that solves that problem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: base.diff
Type: text/x-patch
Size: 1253 bytes
Desc: not available
URL: </pipermail/twisted-python/attachments/20040517/2242c411/attachment-0002.bin>
More information about the Twisted-Python
mailing list