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 2011年10月25日 09:37 by ellioh, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| monotime_unix.py | ellioh, 2011年10月25日 09:37 | A workaround using clock_gettime from librt | ||
| Messages (2) | |||
|---|---|---|---|
| msg146347 - (view) | Author: Elijah Merkin (ellioh) | Date: 2011年10月25日 09:37 | |
time.clock () has very poor time resolution on Linux (tested on Ubuntu 11.04). The result of call to clock () changes once per several seconds. On the other side, on Windows it provides very good resolution. Here is a doctest that fails on Linux: """ >>> from time import sleep >>> prev = clock () >>> res = True >>> for i in xrange(10): ... sleep(0.15) ... next = clock () ... res = res and (next - prev) > 0.1 ... prev = next >>> print res True """ Currently on Linux I am using a workaround that is attached to the issue. |
|||
| msg146348 - (view) | Author: STINNER Victor (vstinner) * (Python committer) | Date: 2011年10月25日 09:39 | |
This issue is a duplicate of the issue #10278. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:23 | admin | set | github: 57470 |
| 2011年10月25日 09:39:26 | vstinner | set | status: open -> closed nosy: + vstinner messages: + msg146348 resolution: duplicate |
| 2011年10月25日 09:37:06 | ellioh | create | |