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 loewis
Recipients brian.curtin, kristjan.jonsson, loewis, pitrou, sbt, tim.golden
Date 2011-03-21.22:52:50
SpamBayes Score 5.2190455e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
> I would still favour committing the semaphore-based version first
> (especially in 3.2), and then discussing performance improvements if
> desired.

For 3.2, I would prefer a solution that makes least changes to the
current code. This is better than fundamentally replacing the
synchronization mechanism which locks are based on.

For 3.3, I predict that any Semaphore-based version will be shortly
replaced by something "fast". Benchmarks seem to indicate that you can
get much faster than semaphores.
Date User Action Args
2011-03-21 22:52:53loewissetrecipients: + loewis, pitrou, kristjan.jonsson, tim.golden, brian.curtin, sbt
2011-03-21 22:52:50loewislinkissue11618 messages
2011-03-21 22:52:50loewiscreate