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 amaury.forgeotdarc, belopolsky, rosslagerwall, vstinner
Date 2012-01-24.13:16:59
SpamBayes Score 2.6183137e-05
Marked as misclassified No
Message-id <CAMpsgwZ84TiU4pPcmMdpX+Jhf=UPFapUvkC4BOXk4ahVtH3tUQ@mail.gmail.com>
In-reply-to <1327405788.06.0.199136694727.issue13845@psf.upfronthosting.co.za>
Content
> NtSetTimerResolution is a system-wide change, and may have impact on other running applications.  It may be an option to set it during the execution of profile.run() for example, but I would not enable it just to call time.clock().

I was not proposing to call, but it was trying to say that under
certain circumstances, you may have a better resolution than 15 ms.
Python should not limit the resolution if the OS provides a better
resolution.
History
Date User Action Args
2012-01-24 13:17:00vstinnersetrecipients: + vstinner, amaury.forgeotdarc, belopolsky, rosslagerwall
2012-01-24 13:16:59vstinnerlinkissue13845 messages
2012-01-24 13:16:59vstinnercreate