Message157564
| Author |
vstinner |
| Recipients |
anacrolix, neologix, pitrou, python-dev, rhettinger, tasslehoff, vstinner |
| Date |
2012年04月05日.11:29:23 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1333625364.26.0.965631004509.issue14222@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Why do you think monotonic time is needed for the Queue module?
The duration of a timeout of N seconds should be N seconds even if the system clock is updated (e.g. a daylight saving time (DST) change).
This feature is checked by an unit test in the patch attached to the isuse #14428 (implementation of the PEP 418):
+ def test_monotonic_settime(self):
+ t1 = time.monotonic()
+ realtime = time.clock_gettime(time.CLOCK_REALTIME)
+ # jump backward with an offset of 1 hour
+ time.clock_settime(time.CLOCK_REALTIME, realtime - 3600)
+ t2 = time.monotonic()
+ time.clock_settime(time.CLOCK_REALTIME, realtime)
+ # monotonic must not be affected by system clock updates
+ self.assertGreaterEqual(t2, t1)
You can imagine a similar patch for Queue timeout. |
|