[Python-Dev] PEP 418 is too divisive and confusing and should be postponed (original) (raw)
Lennart Regebro regebro at gmail.com
Thu Apr 5 10:07:12 CEST 2012
- Previous message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Next message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Apr 5, 2012 at 00:45, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Lennart Regebro wrote:
Since the only monotonic clock that can be adjusted by NTP is Linux' CLOCKMONOTONIC, if we avoid it, then time.monotonic() would always give a clock that isn't adjusted by NTP. I thought we decided that NTP adjustment isn't an issue, because it's always gradual.
Well, in timings it is an issue, but perhaps not a big one. :-) In any case, which one we use will not change the API, so if it is decided it is an issue, we can always more to CLOCK_MONOTONIC_RAW in the future, once Linux < 2.6.26 (or whatever it was) is deemed unsupported.
//Lennart
- Previous message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Next message: [Python-Dev] PEP 418 is too divisive and confusing and should be postponed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]