[Python-ideas] time.wallclock() or other similar stuff

[Brian Curtin]

On Tue, Nov 2, 2010 at 14:21, Rob Cliffe <rob.cliffe at btinternet.com> wrote:

> On 02/11/2010 15:35, Antoine Pitrou wrote:
>
>> On Tue, 2 Nov 2010 16:02:47 +0100
>> spir<denis.spir at gmail.com>  wrote:
>>
>>> Imo, "timer" is exactly the proper term
>>>
>> I'm not sure it's the proper term. A timer is often a countdown with a
>> callback. See for example threading.Timer and signal.setitimer.
>>
>>  the issue due to proximity with "time" is real, but far less
>>> important.
>>>
>> I think it would be too easy to use one instead of the other, and get
>> strange semantics (both count in seconds but with slightly different
>> characteristic).
>>
>> Regards
>>
>> Antoine.
>>
>>
>> _______________________________________________
>> Python-ideas mailing list
>> Python-ideas at python.org
>> http://mail.python.org/mailman/listinfo/python-ideas
>>
>>  Well, how about "clock"?
> "time.clock()" seems quite evocative to me.
> Best wishes
> Rob Cliffe


time.clock is already a part of the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20101102/f377ea22/attachment.html>