[Python-Dev] PEP 418: Add monotonic clock (original) (raw)
Stephen J. Turnbull stephen at xemacs.org
Wed Mar 28 18:39:40 CEST 2012
- Previous message: [Python-Dev] PEP 418: Add monotonic clock
- Next message: [Python-Dev] PEP 418: Add monotonic clock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 29, 2012 at 1:14 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
That means choosing a name for the version that falls back to time() if monotonic() isn't available so it can be safely substituted for time.time() without having to worry about platform compatibility implications.
What's wrong with "time.time()" again? As documented in http://docs.python.org/py3k/library/time.html it makes no guarantees, and specifically there is no guarantee that it will ever behave badly. Of course, we'll have to guarantee that, if a badly-behaved clock is available, users can get access to it, so call that time._time().
- Previous message: [Python-Dev] PEP 418: Add monotonic clock
- Next message: [Python-Dev] PEP 418: Add monotonic clock
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]