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

[exarkun at divmod.com]

On Tue, 2 Nov 2004 10:26:30 +1100, Christopher Armstrong <radeex at gmail.com> wrote:
>Has that bug involving
> callLater(0)-being-run-in-this-iteration-instead-of-the-next-one been
> fixed? We've always said that callLater(0) goes into the next
> iteration, and that's a very useful thing, and I think we should
> ensure that Twisted has this behavior. If it's not fixed, it'd be
> really cool (hint hint) if it were fixed by the time I release 2.0 :)
> 

  A test case was recently added that covers this behavior.  It isn't failing now, although whether this is because:

    1) callLater has been fixed
    2) the test is broken
    3) trial is broken

  I have no idea.

  Jp