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 vstinner
Recipients pitrou, vstinner
Date 2012-03-15.00:52:01
SpamBayes Score 1.5120587e-05
Marked as misclassified No
Message-id <1331772722.48.0.0484604711161.issue14309@psf.upfronthosting.co.za>
In-reply-to
Content
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)
History
Date User Action Args
2012-03-15 00:52:02vstinnersetrecipients: + vstinner, pitrou
2012-03-15 00:52:02vstinnersetmessageid: <1331772722.48.0.0484604711161.issue14309@psf.upfronthosting.co.za>
2012-03-15 00:52:01vstinnerlinkissue14309 messages
2012-03-15 00:52:01vstinnercreate