[Python-Dev] A couple of PEP 418 comments (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Fri Apr 13 23:24:27 CEST 2012
- Previous message: [Python-Dev] A couple of PEP 418 comments
- Next message: [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.perfcounter(): process-wide results, comparable from one thread > to another (?) > - time.processtime(): process-wide, by definition
time.monotonic() and time.perfcounter() 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.
- Previous message: [Python-Dev] A couple of PEP 418 comments
- Next message: [Python-Dev] Summary of Python tracker Issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]