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/118204.html below:

[Python-Dev] PEP 418: Add monotonic clock

[Python-Dev] PEP 418: Add monotonic clock [Python-Dev] PEP 418: Add monotonic clockVictor Stinner victor.stinner at gmail.com
Wed Mar 28 12:56:18 CEST 2012
>>> In that case, I don't think time.try_monotonic() is really needed
>>> because we can emulate "time.monotonic()" in software if the platform is
>>> deficient.
>>
>> As I wrote, I don't think that Python should workaround OS bugs. If
>> the OS monotonic clock is not monotonic, the OS should be fixed.
>
> I sympathize with this, but if the idea is that the Python stdlib should
> use time.monotonic() for scheduling, then it needs to always be
> available. Otherwise, we are not going to use it ourselves, and what
> sort of example is that to set?

There is time.hires() if you need a monotonic clock with a fallback to
the system clock.

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