This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2017-08-23 20:47 by winfreak, last changed 2022-04-11 14:58 by admin. This issue is now closed.
Files | ||||
---|---|---|---|---|
File name | Uploaded | Description | Edit | |
timer_testcase.py | winfreak, 2017-08-23 20:47 | |||
test_monotonic.py | winfreak, 2017-08-23 20:47 |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:58:51 | admin | set | github: 75450 |
2021-10-01 08:49:02 | vstinner | set | superseder: Use the monotonic clock for thread conditions on POSIX platforms -> threading.Condition.wait(timeout) should use a monotonic clock: use pthread_condattr_setclock(CLOCK_MONOTONIC) |
2019-01-17 10:04:50 | vstinner | set | status: open -> closed superseder: Use the monotonic clock for thread conditions on POSIX platforms messages: + msg333840 resolution: duplicate stage: resolved |
2019-01-16 22:26:11 | vstinner | set | messages: + msg333798 |
2018-07-27 10:37:15 | anikey | set | nosy:
+ anikey |
2017-10-09 09:33:52 | vstinner | set | messages: + msg303934 |
2017-10-08 02:04:38 | winfreak | set | messages: + msg303893 |
2017-09-15 14:55:02 | vstinner | set | title: threading.Timer object is affected by changes to system time -> threading.Timer object is affected by changes to system time: Python locks should use a monotonic clock if available |
2017-09-15 14:54:35 | vstinner | set | messages: + msg302259 |
2017-09-15 14:32:44 | vstinner | set | messages: + msg302257 |
2017-09-15 12:52:25 | Matthias Schmidt | set | nosy:
+ Matthias Schmidt messages: + msg302249 |
2017-08-24 10:38:51 | pitrou | set | nosy:
+ vstinner |
2017-08-23 20:47:45 | winfreak | set | files: + test_monotonic.py |
2017-08-23 20:47:35 | winfreak | create |