Message155541
| Author |
nicholas.riley |
| Recipients |
nicholas.riley, vstinner |
| Date |
2012年03月13日.00:38:46 |
| SpamBayes Score |
0.011891628 |
| Marked as misclassified |
No |
| Message-id |
<1331599128.0.0.616247297906.issue14277@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年03月13日 00:38:48 | nicholas.riley | set | recipients:
+ nicholas.riley, vstinner |
| 2012年03月13日 00:38:47 | nicholas.riley | set | messageid: <1331599128.0.0.616247297906.issue14277@psf.upfronthosting.co.za> |
| 2012年03月13日 00:38:47 | nicholas.riley | link | issue14277 messages |
| 2012年03月13日 00:38:47 | nicholas.riley | create |
|