On Nov 15, 2011, at 9:57 AM, exarkun@twistedmatrix.com wrote:

On 02:33 pm, tobias.oberstein@tavendo.de wrote:

...

2 short questions .. please consider:

a) reactor.callLater(0, fun1) reactor.callLater(0, fun2)

Is that allowed .. delay == 0? It seems to work .. but I want to be sure.

Yep. It's allowed. It means to run the function pretty soon, but not right now.

...

b) reactor.callLater(T, fun1) reactor.callLater(T, fun2)

Is the call _order_ first fun1, then fun2 _guaranteed_? For every T, and in particular T == 0?

This isn't guaranteed. It's been proposed that it should be, but the ticket has been languishing for a few years now:

http://twistedmatrix.com/trac/ticket/1396

You might want to look at twisted.internet.task.cooperate instead if you want to perform a sequence of functions separated by callLater()s. -glyph

On Nov 15, 2011, at 9:57 AM, exarkun@twistedmatrix.com wrote:

On 02:33 pm, tobias.oberstein@tavendo.de wrote:

...

2 short questions .. please consider:

a) reactor.callLater(0, fun1) reactor.callLater(0, fun2)

Is that allowed .. delay == 0? It seems to work .. but I want to be sure.

Yep. It's allowed. It means to run the function pretty soon, but not right now.

...

b) reactor.callLater(T, fun1) reactor.callLater(T, fun2)

Is the call _order_ first fun1, then fun2 _guaranteed_? For every T, and in particular T == 0?

This isn't guaranteed. It's been proposed that it should be, but the ticket has been languishing for a few years now:

http://twistedmatrix.com/trac/ticket/1396

You might want to look at twisted.internet.task.cooperate instead if you want to perform a sequence of functions separated by callLater()s. -glyph