[Python-Dev] Drop the new time.wallclock() function?
Antoine Pitrou
solipsis at pitrou.net
Wed Mar 14 10:16:18 CET 2012
More information about the Python-Dev mailing list
Wed Mar 14 10:16:18 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 ]
On Wed, 14 Mar 2012 02:03:42 +0100 Victor Stinner <victor.stinner at gmail.com> wrote: > > We may merge both functions with a flag to be able to disable the > fallback. Example: > > - time.realtime(): best-effort monotonic, with a fallback > - time.realtime(monotonic=True): monotonic, may raise OSError or > NotImplementedError That's a rather awful name. time.time() is *the* real time. time.monotonic(fallback=False) would be a better API. Regards Antoine.
- 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