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

[Python-Dev] A couple of PEP 418 comments

[Python-Dev] A couple of PEP 418 commentsAntoine Pitrou solipsis at pitrou.net
Fri Apr 13 23:24:27 CEST 2012
On Fri, 13 Apr 2012 18:29:10 +0200
Victor Stinner <victor.stinner at gmail.com> wrote:
> > The descriptions should really stress the scope of the result's
> > validity. My guess (or wish :-)) would be:
> >
> > - time.monotonic(): system-wide results, comparable from one process to
> >  another
> > - time.perf_counter(): process-wide results, comparable from one thread
> >  to another (?)
> > - time.process_time(): process-wide, by definition
> 
> time.monotonic() and time.perf_counter() are process-wide on Windows
> older than Vista because of GetTickCount() overflow, on other OSes,
> they are system-wide.

Perhaps, but you should say in the PEP, not here ;-)
By the way, I wonder if it may be a problem if monotonic() is
process-wide under Windows.

> All OSes provide a monotonic clock, except GNU/Hurd. You mean that it
> should be mentioned in the time.monotonic() section?

Yes, that would be clearer.

Regards

Antoine.


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