[issue10278] add time.wallclock() method

Alexander Belopolsky report at bugs.python.org
Mon Nov 1 18:55:44 CET 2010


Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:

On Mon, Nov 1, 2010 at 1:43 PM, Antoine Pitrou <report at bugs.python.org> wrote:
..
> Well, the problem is that the "appropriate test" is not easy to guess a priori, so it would
> be useful for the stdlib to provide the right tool for the job.

This sounds like an argument against this feature, not for it.  If it
is hard for the application code to implement an appropriate test "a
priori", what is the chance to get it right in stdlib?

> As for where it should live, I have no strong opinion, but it's true that the time module looks appropriate.

Having time.time and time.clock is already confusing enough.  Having
the third function which is either the first or the second depending
on some unspecified criterion does not strike me as a clean design.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10278>
_______________________________________


More information about the Python-bugs-list mailing list