[Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default (original) (raw)
Victor Stinner victor.stinner at gmail.com
Tue Mar 20 10:33:11 CET 2012
- Previous message: [Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default
- Next message: [Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think this discussion has veered off a bit into the overly-theoretical. Python cannot really "guarantee" anything here
That's why the function name was changed from time.monotonic() to time.steady(strict=True). If you want to change something, you should change the documentation to list OS limitations.
It's the OS's job to guarantee things
Correct, most Python modules exposing OS functions are thin wrappers and don't add any magic. When we need a higher level API, we write a new module: like shutil enhancing the os module.
Victor
- Previous message: [Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default
- Next message: [Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]