A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/117828.html below:

[Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default

[Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by default [Python-Dev] cpython: Issue #10278: Add an optional strict argument to time.steady(), False by defaultVictor Stinner victor.stinner at gmail.com
Tue Mar 20 10:33:11 CET 2012
> 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4