➜

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 vstinner
Recipients Alexander.Belopolsky, Arfrever, belopolsky, ericography, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rhettinger, rosslagerwall, skrah, vstinner
Date 2012-01-24.01:25:37
SpamBayes Score 0.00010020225
Marked as misclassified No
Message-id <1327368338.75.0.94048788967.issue11457@psf.upfronthosting.co.za>
In-reply-to
Content 
With the new function time.wallclock() and time.clock_gettime() (issue #10278), and maybe time.monotonic() will maybe be also added (issue #13846), I now agree that it is important to support t2-t1 to compute a difference. Using a tuple, it's not easy to compute a difference.

time.wallclock(), time.clock_gettime() and time.monotonic() have a nanosecond resolution on Linux. Using issue #13845, time.time() will have a resolution of 100 ns on Windows.
History
Date User Action Args
2012-01-24 01:25:38vstinnersetrecipients: + vstinner, loewis, rhettinger, jcea, mark.dickinson, belopolsky, lars.gustaebel, larry, nadeem.vawda, Arfrever, r.david.murray, skrah, Alexander.Belopolsky, rosslagerwall, khenriksson, ericography
2012-01-24 01:25:38vstinnersetmessageid: <1327368338.75.0.94048788967.issue11457@psf.upfronthosting.co.za>
2012-01-24 01:25:38vstinnerlinkissue11457 messages
2012-01-24 01:25:37vstinnercreate