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 akira
Recipients akira, docs@python
Date 2014-10-28.07:36:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414481814.68.0.767829383037.issue22749@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-10-28 07:36:54akirasetrecipients: + akira, docs@python
2014-10-28 07:36:54akirasetmessageid: <1414481814.68.0.767829383037.issue22749@psf.upfronthosting.co.za>
2014-10-28 07:36:54akiralinkissue22749 messages
2014-10-28 07:36:54akiracreate