[New-bugs-announce] [issue34054] multiprocessing should use time.monotonic() for timeout

STINNER Victor report at bugs.python.org
Thu Jul 5 12:33:47 EDT 2018


New submission from STINNER Victor <vstinner at redhat.com>:

In different functions, the multiprocessing module uses the system clock: time.time(). The system clock can be updated manually by the system administrator or automatically by NTP (for example).

Attached PR modifies multiprocessing to use time.monotonic() instead to not be affected by system clock changes.

time.monotonic() is always available since Python 3.5. See also the PEP 418.

----------
components: Library (Lib)
messages: 321115
nosy: vstinner
priority: normal
severity: normal
status: open
title: multiprocessing should use time.monotonic() for timeout
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34054>
_______________________________________


More information about the New-bugs-announce mailing list