Message200714
| Author | pitrou |
|---|---|
| Recipients | giampaolo.rodola, pitrou, rhettinger, serhiy.storchaka, vstinner |
| Date | 2013-10-21.08:14:40 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <2090223434.97274731.1382343253940.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to | <1382342229.85.0.320026255111.issue19270@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> 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) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-10-21 08:14:41 | pitrou | set | recipients: + pitrou, rhettinger, vstinner, giampaolo.rodola, serhiy.storchaka |
| 2013-10-21 08:14:41 | pitrou | link | issue19270 messages |
| 2013-10-21 08:14:40 | pitrou | create | |