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 lemburg
Recipients giampaolo.rodola, lemburg, pitrou, vstinner
Date 2012-03-16.18:05:30
SpamBayes Score 7.8322976e-10
Marked as misclassified No
Message-id <4F6380E9.7060905@egenix.com>
In-reply-to <CAMpsgwYqw1b94y8aiRvYfPOC_74Aa9RmMwZ=ZphexXe6GA=U-Q@mail.gmail.com>
Content
STINNER Victor wrote:
> 
> STINNER Victor <victor.stinner@gmail.com> added the comment:
> 
>> time.clock() has been in use for ages in many many scripts.
>> We don't want to carelessly break all those.
> 
> I don't want to remove the function, just mark it as deprecated to
> avoid confusion. It will only be removed from the next major Python.

Why ? There's no other single function providing the same functionality,
so it's not even a candidate for deprecation.

Similar functionality is available via several different functions,
but that's true for a lot functions in th stdlib.
History
Date User Action Args
2012-03-16 18:05:31lemburgsetrecipients: + lemburg, pitrou, vstinner, giampaolo.rodola
2012-03-16 18:05:31lemburglinkissue14309 messages
2012-03-16 18:05:30lemburgcreate