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 ronaldoussoren
Recipients belopolsky, jab, ned.deily, njs, nooB, p-ganssle, ronaldoussoren, vstinner, xrisk
Date 2020-08-06.09:51:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596707508.82.0.435562980147.issue41303@roundup.psfhosted.org>
In-reply-to
Content
mach_absolute_time returns time in ticks, there's a separate API that returns the resolution of this clock (which is already used).

The manpage explicitly says that mach_absolute_time and CLOCK_UPTIME_RAW are the same clock:

     CLOCK_UPTIME_RAW   clock that increments monotonically, in the same manner as CLOCK_MONOTONIC_RAW, but that does
                        not increment while the system is asleep.  The returned value is identical to the result of
                        mach_absolute_time() after the appropriate mach_timebase conversion is applied.

Switching from mach_absolute_time to CLOCK_UPTIME_RAW would therefore bring us no improvements, and would complicate the code base because clock_gettime is only available starting from macOS 10.12.
History
Date User Action Args
2020-08-06 09:51:48ronaldoussorensetrecipients: + ronaldoussoren, belopolsky, vstinner, ned.deily, njs, jab, nooB, p-ganssle, xrisk
2020-08-06 09:51:48ronaldoussorensetmessageid: <1596707508.82.0.435562980147.issue41303@roundup.psfhosted.org>
2020-08-06 09:51:48ronaldoussorenlinkissue41303 messages
2020-08-06 09:51:48ronaldoussorencreate