Issue #22043: time.monotonic() is now always available
authorVictor Stinner <victor.stinner@gmail.com>
Tue, 2 Sep 2014 21:18:25 +0000 (23:18 +0200)
committerVictor Stinner <victor.stinner@gmail.com>
Tue, 2 Sep 2014 21:18:25 +0000 (23:18 +0200)
commitae58649721ec898ea4a101b0861e16fff3511cfa
treebb08b1a9b5f354212d7ca365d76659b09aed879a
parent9bb758cee7f1694807ebe600b6230fb8e565d3ea
Issue #22043: time.monotonic() is now always available

threading.Lock.acquire(), threading.RLock.acquire() and socket operations now
use a monotonic clock, instead of the system clock, when a timeout is used.
17 files changed:
Doc/library/time.rst
Doc/whatsnew/3.5.rst
Include/pytime.h
Lib/queue.py
Lib/sched.py
Lib/socketserver.py
Lib/subprocess.py
Lib/telnetlib.py
Lib/test/test_selectors.py
Lib/threading.py
Lib/trace.py
Misc/NEWS
Modules/_threadmodule.c
Modules/gcmodule.c
Modules/socketmodule.c
Modules/timemodule.c
Python/pytime.c