[Python-Dev] an alternative to embedding policy in PEP 418 (original) (raw)
Victor Stinner victor.stinner at gmail.com
Fri Apr 6 00:27:16 CEST 2012
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 06/04/2012 00:17, Cameron Simpson a écrit :
This is where the bitmap approach can be less confusing - the docstring says "The returned clock shall have all the requested flags". It is at least very predictable.
By the way, I removed ("deferred") the time.highres() function from the PEP, and I try to avoid the term "steady" because no OS clock respect the definition of "steady" (especially in corner cases as system suspend/resume). So which flags do you want to support? (only "monotonic"?)
Basically, get_clock("monotonic") should give time.monotonic() whereas get_clock() gives time.time()?
Victor
- Previous message: [Python-Dev] an alternative to embedding policy in PEP 418
- Next message: [Python-Dev] an alternative to embedding policy in PEP 418
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]