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

[Python-Dev] an alternative to embedding policy in PEP 418

[Python-Dev] an alternative to embedding policy in PEP 418 [Python-Dev] an alternative to embedding policy in PEP 418Victor Stinner victor.stinner at gmail.com
Fri Apr 6 00:27:16 CEST 2012
Le 06/04/2012 00:17, Cameron Simpson a écrit :
> This is where the bitmap approach can be less confusing - the docstring
> says "The returned clock shall have all the requested flags". It is at
> least very predictable.

By the way, I removed ("deferred") the time.highres() function from the 
PEP, and I try to avoid the term "steady" because no OS clock respect 
the definition of "steady" (especially in corner cases as system 
suspend/resume). So which flags do you want to support? (only "monotonic"?)

Basically, get_clock("monotonic") should give time.monotonic() whereas 
get_clock() gives time.time()?

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