➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients giampaolo.rodola, pitrou, rhettinger, serhiy.storchaka, vstinner
Date 2013-10-21.07:57:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382342229.85.0.320026255111.issue19270@psf.upfronthosting.co.za>
In-reply-to
Content 
> That is allowed.   We make no stability guarantees.  Plus it just makes sense that events with the same time and priority are non-deterministic.

It would be nice to keep the insertion order. If it is not guaranteed, it must be well documented (big red warning).

Does it occur frequently to schedule two events at exactly the same time? On Linux, clocks have a good precision, even time.monotonic(). On Windows, the precision of time.monotonic() is worse (around 16 ms), so two events at the same time is more likely.

The issue is specific to events scheduled at an absolute time, right? Or does .enter() has a similar issue?
History
Date User Action Args
2013-10-21 07:57:09vstinnersetrecipients: + vstinner, rhettinger, pitrou, giampaolo.rodola, serhiy.storchaka
2013-10-21 07:57:09vstinnersetmessageid: <1382342229.85.0.320026255111.issue19270@psf.upfronthosting.co.za>
2013-10-21 07:57:09vstinnerlinkissue19270 messages
2013-10-21 07:57:09vstinnercreate