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 beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, techtonik, torsten
Date 2010-04-11.14:59:04
SpamBayes Score 1.6425373e-08
Marked as misclassified No
Message-id <1270998068.3494.11.camel@localhost>
In-reply-to <1270997187.54.0.0415144685384.issue8299@psf.upfronthosting.co.za>
Content
> Antoine (2):  The need to have do_yield is a symptom of the brokenness
> of the GIL.

Of course it is. But the point of the benchmark is to give valid results
even with the old broken GIL.

I could remove do_yield and still have it give valid results, but that
would mean running each step for 30 seconds instead of 2. I don't like
having to wait several minutes for benchmark numbers :-)
History
Date User Action Args
2010-04-11 14:59:06pitrousetrecipients: + pitrou, loewis, beazley, kristjan.jonsson, techtonik, flox, dabeaz, torsten
2010-04-11 14:59:05pitroulinkissue8299 messages
2010-04-11 14:59:04pitroucreate