diff options
| author | Victor Stinner <victor.stinner@gmail.com> | 2015-09-03 00:13:46 +0200 |
|---|---|---|
| committer | Victor Stinner <victor.stinner@gmail.com> | 2015-09-03 00:13:46 +0200 |
| commit | c3c616c3d193c211bd435380593a20ec13e07b7b (patch) | |
| tree | d71ab0c1bdb5c88362dc8e39e089a3add8f265f5 /Python/mysnprintf.c | |
| parent | 4912e7a3fd0c78d630b8e571d35c2968eb4b586c (diff) | |
| download | cpython-git-c3c616c3d193c211bd435380593a20ec13e07b7b.tar.gz | |
Issue #24707: Remove assertion in monotonic clock
Don't check anymore at runtime that the monotonic clock doesn't go backward.
Yes, it happens. It occurs sometimes each month on a Debian buildbot slave
running in a VM.
The problem is that Python cannot do anything useful if a monotonic clock goes
backward. It was decided in the PEP 418 to not fix the system, but only expose
the clock provided by the OS.
Diffstat (limited to 'Python/mysnprintf.c')
0 files changed, 0 insertions, 0 deletions