[issue14277] time.monotonic docstring does not mention the time unit returned

[Nicholas Riley]

Nicholas Riley <com-python-bugs at sabi.net> added the comment:

According to http://juliusdavies.ca/posix_clocks/clock_realtime_linux_faq.html, CLOCK_REALTIME can go backwards. CLOCK_MONOTONIC_RAW is best where available (like QueryPerformanceFrequency / mach_absolute_time) and CLOCK_MONOTONIC is pretty good.

So I have updated both the docs for time.monotonic and time.wallclock to hopefully better explain things... may need to be another issue here too.

----------
keywords: +patch
Added file: http://bugs.python.org/file24809/monotonic-doc.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14277>
_______________________________________