Skip to main content

Browse the archive

Staging
v0.8.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 2b01121fd4200f1c27873422f7f72d02eec08630 authored by Miss Islington (bot) on 27 September 2018, 11:46:38 UTC, committed by GitHub on 27 September 2018, 11:46:38 UTC 
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.
(cherry picked from commit a94ee12c26aa8dd7dce01373779df8055aff765b)

Co-authored-by: orlnub123 <orlnub123@gmail.com>
1 parent 2bdba6b
Raw File
Tip revision: 2b01121fd4200f1c27873422f7f72d02eec08630 authored by Miss Islington (bot) on 27 September 2018, 11:46:38 UTC
bpo-34819: Use a monotonic clock to compute timeouts in concurrent.futures (GH-9599)
Tip revision: 2b01121
CODE_OF_CONDUCT.rst 
Code of Conduct
===============

Please note that all interactions on
`Python Software Foundation <https://www.python.org/psf-landing/>`__-supported
infrastructure is `covered
<https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties>`__
by the `PSF Code of Conduct <https://www.python.org/psf/codeofconduct/>`__,
which includes all infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general this means everyone is expected to be open, considerate, and
respectful of others no matter what their position is within the project.
back to top