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 brian.curtin, jnoller, lemburg, nascheme, pitrou, rcohen, schmir
Date 2010-01-22.14:23:25
SpamBayes Score 7.3452266e-10
Marked as misclassified No
Message-id <1264170208.67.0.155651352106.issue7753@psf.upfronthosting.co.za>
In-reply-to
Content
>  * Instead of deprecating the set/getcheckinterval APIs, convert the
> arguments passed to these to the switch interval. The new APIs
> set/getswitchinteral are then not needed.

This is certainly not a good idea. The semantics are different, which is the reason why I created a separate API in the first place instead of recycling the old one.

Actually, there should be hardly any reason to want to change the interval with the new GIL implementation. It was required with the old GIL due to the fact that counting opcodes is a very poor way of estimating wall clock durations.

> Note that gettimeofday() et al. are rather slow APIs on most systems

In my measurements under Linux it seemed to be as fast as clock_gettime() actually. But I don't know about other systems. I didn't want to complicate the patch (with several different paths) more than seemed necessary.
History
Date User Action Args
2010-01-22 14:23:28pitrousetrecipients: + pitrou, lemburg, nascheme, schmir, jnoller, brian.curtin, rcohen
2010-01-22 14:23:28pitrousetmessageid: <1264170208.67.0.155651352106.issue7753@psf.upfronthosting.co.za>
2010-01-22 14:23:26pitroulinkissue7753 messages
2010-01-22 14:23:25pitroucreate