[issue14309] Deprecate time.clock()
Marc-Andre Lemburg
report at bugs.python.org
Thu Mar 15 07:37:48 CET 2012
Marc-Andre Lemburg <mal at egenix.com> added the comment:
STINNER Victor wrote:
>
> New submission from STINNER Victor <victor.stinner at gmail.com>:
>
> Python 3.3 has 3 functions to get time:
>
> - time.clock()
> - time.steady()
> - time.time()
>
> Antoine Pitrou suggested to deprecated time.clock() in msg120149 (issue #10278).
>
> "The problem is time.clock(), since it does two wildly different things
> depending on the OS. I would suggest to deprecate time.clock() at the same time as we add time.wallclock(). For the Unix-specific definition of time.clock(), there is already os.times() (which gives even richer information)."
>
> (time.wallclock was the old name of time.steady)
Strong -1 on this idea.
time.clock() has been in use for ages in many many scripts. We don't
want to carelessly break all those.
----------
nosy: +lemburg
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14309>
_______________________________________
More information about the Python-bugs-list
mailing list