Author lemburg
Recipients lemburg, pitrou, vstinner
Date 2012-03-15.06:37:48
SpamBayes Score 3.53748e-07
Marked as misclassified No
Message-id <4F618E38.7020108@egenix.com>
In-reply-to <1331772722.48.0.0484604711161.issue14309@psf.upfronthosting.co.za>
Content
STINNER Victor wrote:
> 
> New submission from STINNER Victor <victor.stinner@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.
History
Date User Action Args
2012-03-15 06:37:49lemburgsetrecipients: + lemburg, pitrou, vstinner
2012-03-15 06:37:48lemburglinkissue14309 messages
2012-03-15 06:37:48lemburgcreate