[issue14690] Use monotonic time for sched, trace and subprocess modules

Roundup Robot added the comment: New changeset 1345cf58738d by Victor Stinner in branch 'default': Close #14690: Use monotonic clock instead of system clock in the sched, http://hg.python.org/cpython/rev/1345cf58738d -- nosy: +python-dev resolution: -> fixed stage: -> committed/reject

[issue14690] Use monotonic time for sched, trace and subprocess modules

Charles-François Natali added the comment: LGTM. Juste one nitpick: why do you sometimes import the clock source as get_time() and others _time()? _time() looks fine to me. -- ___ Python tracker _

[issue14690] Use monotonic time for sched, trace and subprocess modules

Changes by STINNER Victor : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue14690] Use monotonic time for sched, trace and subprocess modules

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue14690] Use monotonic time for sched, trace and subprocess modules

New submission from STINNER Victor : The PEP 418 added a new time.monotonic() function. The sched, trace and subprocess modules should use it, if available, to avoid issues when the system time is changed. Attached patch uses the time.monotonic() function when available. See also the issue #1