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.
| Author | anacrolix |
|---|---|
| Recipients | anacrolix, belopolsky, eric.araujo, glenn, kristjan.jonsson, michael.foord, pitrou, vstinner |
| Date | 2011年01月14日.09:20:25 |
| SpamBayes Score | 0.0061686886 |
| Marked as misclassified | No |
| Message-id | <1294996829.5.0.671439625759.issue10278@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This is sorely needed. IMO the current behaviour of time.clock works for Windows, and clock_gettime(CLOCK_MONOTONIC) on POSIX or clock_gettime(CLOCK_MONOTONIC_RAW) on Linux>=2.6.28. There are some related discussions on StackOverflow that may contain useful ideas also: http://stackoverflow.com/questions/1205722/how-do-i-get-monotonic-time-durations-in-python http://stackoverflow.com/questions/4687408/retrieve-wall-time-in-python-using-the-standard-library |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年01月14日 09:20:29 | anacrolix | set | recipients: + anacrolix, belopolsky, pitrou, kristjan.jonsson, vstinner, eric.araujo, michael.foord, glenn |
| 2011年01月14日 09:20:29 | anacrolix | set | messageid: <1294996829.5.0.671439625759.issue10278@psf.upfronthosting.co.za> |
| 2011年01月14日 09:20:25 | anacrolix | link | issue10278 messages |
| 2011年01月14日 09:20:25 | anacrolix | create | |