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 pitrou
Recipients MrJean1, alexandre.vassalotti, gregory.p.smith, pitrou
Date 2009-11-25.23:32:47
SpamBayes Score 0.0028617678
Marked as misclassified No
Message-id <1259191970.82.0.77039009027.issue2281@psf.upfronthosting.co.za>
In-reply-to
Content
One issue with using timestamp counters is that their resolution varies
with CPU speed, which is not necessarily constant during a whole run
(because of power management). On the other hand I'm not sure it's
really a problem.
History
Date User Action Args
2009-11-25 23:32:50pitrousetrecipients: + pitrou, gregory.p.smith, alexandre.vassalotti, MrJean1
2009-11-25 23:32:50pitrousetmessageid: <1259191970.82.0.77039009027.issue2281@psf.upfronthosting.co.za>
2009-11-25 23:32:48pitroulinkissue2281 messages
2009-11-25 23:32:48pitroucreate