[issue14309] Deprecate time.clock()

STINNER Victor added the comment: The PEP 418 has been accepted: read it to understand why time.clock() is now deprecated. -- ___ Python tracker ___ ___

[issue14309] Deprecate time.clock()

Roundup Robot added the comment: New changeset 314c3faea2fb by Victor Stinner in branch 'default': Close #14309: Deprecate time.clock() http://hg.python.org/cpython/rev/314c3faea2fb -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue14309] Deprecate time.clock()

STINNER Victor added the comment: > Something can be done to provide portable functions to get > the user and system times. Lib/profile.py tests also various functions to choose the best one in Profile constructor. -- ___ Python tracker

[issue14309] Deprecate time.clock()

STINNER Victor added the comment: I misunderstood the time.clock() function. It counts the CPU time while the process is active, whereas a monotonic clock counts elapsed time even during a sleep. time.clock() and time.monotonic() are different clocks for different purposes. I wrote the PEP 4

[issue14309] Deprecate time.clock()

Marc-Andre Lemburg added the comment: STINNER Victor wrote: > > STINNER Victor added the comment: > >> There's no other single function providing the same functionality > > time.clock() is not portable: it is a different clock depending on the OS. To > write portable code, you have to use t

[issue14309] Deprecate time.clock()

STINNER Victor added the comment: > There's no other single function providing the same functionality time.clock() is not portable: it is a different clock depending on the OS. To write portable code, you have to use the right function: - time.time() - time.steady() - os.times(), resource.

[issue14309] Deprecate time.clock()

Marc-Andre Lemburg added the comment: STINNER Victor wrote: > > STINNER Victor 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 co

[issue14309] Deprecate time.clock()

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue14309] Deprecate time.clock()

STINNER Victor 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. -- ___

[issue14309] Deprecate time.clock()

Marc-Andre Lemburg added the comment: STINNER Victor wrote: > > New submission from STINNER Victor : > > 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). >

[issue14309] Deprecate time.clock()

New submission from STINNER Victor : 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