[ pycrypto-Patches-1258276 ] time.time -> time.clock

"SourceForge.net" <[email protected]> Sat, 13 Aug 2005 01:26:13 -0700
Newsgroups gmane.comp.python.cryptography.cvs
Message-ID <[email protected]>
Patches item #1258276, was opened at 2005-08-13 08:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=320937&aid=1258276&group_id=20937

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Erik Andersén (erik_andersen)
Assigned to: Nobody/Anonymous (nobody)
Summary: time.time -> time.clock

Initial Comment:
When timing, the test program often says that the
program executed to fast to measure the time 
used.

To time a program, time.clock should be used 
instead of time.time. The former will give better 
resolution, at least on some systems.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=320937&aid=1258276&group_id=20937


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf