[issue19270] sched.cancel() breaks events order
Antoine Pitrou
report at bugs.python.org
Mon Oct 21 10:14:41 CEST 2013
Antoine Pitrou added the comment:
> Does it occur frequently to schedule two events at exactly the same
> time? On Linux, clocks have a good precision, even time.monotonic().
It depends how you calculate your timestamps, I'd say :-) It's unlikely
for two calls to time.time() to give the exact same outcome. OTOH, if
you're using a fixed base time and add user-provided timedeltas to it,
collisions are quite possible.
(a special case is using a 0 delay, in order to schedule a call for
the next loop iteration)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19270>
_______________________________________
More information about the Python-bugs-list
mailing list