[Python-Dev] Rename time.steady(strict=True) to time.monotonic()? (original) (raw)
Victor Stinner victor.stinner at gmail.com
Sat Mar 24 11:35:43 CET 2012
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Does this mean that there are circumstances where monotonic will work for a while, but then fail?
No. time.monotonic() always work or always fail. If monotonic() failed, steady() doesn't call it again.
Otherwise, we would only need to check monotonic once, when the time module is first loaded, rather than every time it is called. Instead of the above:
# global to the time module try: monotonic() except (NameError, OSError): steady = time else: steady = monotonic
I implemented steady differently to avoid the need of calling monotonic at Python startup. Calling monotonic at startup would be an extra useless system call.
Victor
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]