➜
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 2014-10-28 07:36 by akira, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| docs-time-clock-remove-stale-remark.diff | akira, 2014-10-28 07:36 | review | ||
| Messages (3) | |||
|---|---|---|---|
| msg230124 - (view) | Author: Akira Li (akira) * | Date: 2014-10-28 07:36 | |
time.clock() documentation [1] says: this is the function to use for benchmarking Python or timing algorithms. and Deprecated since version 3.3: The behaviour of this function depends on the platform: use perf_counter() or process_time() instead, depending on your requirements, to have a well defined behaviour. [1]: https://hg.python.org/cpython/file/a22ef88143b9/Doc/library/time.rst#l127 The first remark is incorrect since 3.3. I've attached a documentation patch that removes it. |
|||
| msg230126 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2014-10-28 08:18 | |
LGTM. |
|||
| msg230173 - (view) | Author: Roundup Robot (python-dev)  |
Date: 2014-10-28 20:35 | |
New changeset 5f086db3b51b by Georg Brandl in branch '3.4': Closes #22749: remove outdated advice to use clock() for accurate timing. https://hg.python.org/cpython/rev/5f086db3b51b |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:09 | admin | set | github: 66938 |
| 2014-10-28 20:35:51 | python-dev | set | status: open -> closed nosy: + python-dev messages: + msg230173 resolution: fixed stage: resolved |
| 2014-10-28 08:18:47 | georg.brandl | set | nosy:
+ georg.brandl messages: + msg230126 |
| 2014-10-28 07:36:54 | akira | create | |