From 3ab064e80a9be1e6e9c62437fffb92bde9c5e1fb Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Mon, 17 Dec 2018 12:12:34 +0100 Subject: bpo-23451: Update time.monotonic() documentation (GH-11190) bpo-23451, bpo-22117: Python 3.5 requires Windows Vista or newer, time.monotonic() is now always system-wide. --- Doc/library/time.rst | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/Doc/library/time.rst b/Doc/library/time.rst index c6a1f33..0ffce47 100644 --- a/Doc/library/time.rst +++ b/Doc/library/time.rst @@ -293,17 +293,9 @@ Functions The reference point of the returned value is undefined, so that only the difference between the results of consecutive calls is valid. - On Windows versions older than Vista, :func:`monotonic` detects - :c:func:`GetTickCount` integer overflow (32 bits, roll-over after 49.7 days). - It increases an internal epoch (reference time) by 2\ :sup:`32` each time - that an overflow is detected. The epoch is stored in the process-local state - and so the value of :func:`monotonic` may be different in two Python - processes running for more than 49 days. On more recent versions of Windows - and on other operating systems, :func:`monotonic` is system-wide. - .. versionadded:: 3.3 .. versionchanged:: 3.5 - The function is now always available. + The function is now always available and always system-wide. .. function:: monotonic_ns() -> int -- cgit v0.12