[Python-Dev] Drop the new time.wallclock() function?
Nadeem Vawda
nadeem.vawda at gmail.com
Wed Mar 14 01:18:26 CET 2012
More information about the Python-Dev mailing list
Wed Mar 14 01:18:26 CET 2012
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So wallclock() falls back to a not-necessarily-monotonic time source if necessary, while monotonic() raises an exception in that case? ISTM that these don't need to be separate functions - rather, we can have one function that takes a flag (called require_monotonic, or something like that) telling it which failure mode to use. Does that make sense? Cheers, Nadeem
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list