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 belopolsky
Recipients belopolsky, eric.araujo, kristjan.jonsson, michael.foord, pitrou
Date 2010-11-01.17:55:42
SpamBayes Score 1.3411866e-10
Marked as misclassified No
Message-id <AANLkTi=Oauu2q1z5dYembm+ARz_y3ifdYLxODq_D9F_b@mail.gmail.com>
In-reply-to <1288633398.27.0.455727731436.issue10278@psf.upfronthosting.co.za>
Content
On Mon, Nov 1, 2010 at 1:43 PM, Antoine Pitrou <report@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.
History
Date User Action Args
2010-11-01 17:55:44belopolskysetrecipients: + belopolsky, pitrou, kristjan.jonsson, eric.araujo, michael.foord
2010-11-01 17:55:42belopolskylinkissue10278 messages
2010-11-01 17:55:42belopolskycreate