This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Nitapol, lukasz.langa, ned.deily, rhettinger, ronaldoussoren, vstinner
Date 2019-08-26.10:55:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> process_time: namespace(adjustable=False, implementation='clock_gettime(CLOCK_PROCESS_CPUTIME_ID)', monotonic=True, resolution=1.0000000000000002e-06)

Using CLOCK_PROCESS_CPUTIME_ID clock for time.process_time() looks good to me. I don't know why depending on how Python is built, you get a different clock.

> process_time: namespace(adjustable=False, implementation='getrusage(RUSAGE_SELF)', monotonic=True, resolution=1e-06)

It should be the same clock than CLOCK_PROCESS_CPUTIME_ID, maybe with a different resolution.

If both are available, we should prefer the clock with the best *effective* resolution.
Date User Action Args
2019-08-26 10:55:24vstinnersetrecipients: + vstinner, rhettinger, ronaldoussoren, ned.deily, lukasz.langa, Nitapol
2019-08-26 10:55:24vstinnersetmessageid: <>
2019-08-26 10:55:24vstinnerlinkissue36205 messages
2019-08-26 10:55:24vstinnercreate