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

[Python-Dev] Drop the new time.wallclock() function?

[Python-Dev] Drop the new time.wallclock() function? [Python-Dev] Drop the new time.wallclock() function?Lennart Regebro regebro at gmail.com
Wed Mar 14 19:07:29 CET 2012
2012/3/14 Kristján Valur Jónsson <kristjan at ccpgames.com>:
>> - By default, it should fall back to time.time if a better source is
>>  not available, but there should be a flag that can disable this
>>  fallback for users who really *need* a monotonic/steady time source.
> As pointed out on a different thread, you don"t need this "flag" since the code can easily enforce the monotonic property by maintaining a static value.

With this, I think time.steady() would be clear and nice.

//Lennart
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