]> granicus.if.org Git - python/commit
bpo-34819: Use a monotonic clock to compute timeouts in concurrent.futures (GH-9599)
authororlnub123 <orlnub123@gmail.com>
Thu, 27 Sep 2018 11:16:26 +0000 (14:16 +0300)
committerAntoine Pitrou <pitrou@free.fr>
Thu, 27 Sep 2018 11:16:26 +0000 (13:16 +0200)
commita94ee12c26aa8dd7dce01373779df8055aff765b
tree1b627f9fac54e8b0d6a88c8f62ecd785b40a5b8b
parent7291108d88ea31d205da4db19d202d6cbffc6d93
bpo-34819: Use a monotonic clock to compute timeouts in concurrent.futures (GH-9599)

Use a monotonic clock to compute timeouts in :meth:`Executor.map` and :func:`as_completed`, in order to prevent timeouts from deviating when the system clock is adjusted.

This may not be sufficient on all systems. On POSIX for example, the actual waiting (e.g. in ``sem_timedwait``) is specified to rely on the CLOCK_REALTIME clock.
Lib/concurrent/futures/_base.py
Misc/NEWS.d/next/Library/2018-09-27-09-45-00.bpo-34819.9ZaFyO.rst [new file with mode: 0644]