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 barry, pitrou, rbcollins, statik
Date 2009-10-26.21:27:30
SpamBayes Score 0.00050419604
Marked as misclassified No
Message-id <1256596288.3923.11.camel@localhost>
In-reply-to <1256591705.7720.4.camel@lifeless-64>
Content
> Looks fine to me assuming that the locking functions can be used outside
> the GIL.

Yes, they can. Actually, even the GIL uses them. :-)

> On the test side, the case I supplied was low noise for me - I'd
> hesitate to do as much compression as you are (50 times more) unless you
> saw it spuriously pass a lot - the nature of the deadlock isn't
> dependent on races so much as simple scheduling - as long as the seocnd
> thread is scheduled before the first thread completes compressing the
> deadlock will occur.

Well, your test case often succeeded here, so I decided on a more
aggressive variation.
History
Date User Action Args
2009-10-26 21:27:34pitrousetrecipients: + pitrou, barry, rbcollins, statik
2009-10-26 21:27:30pitroulinkissue7205 messages
2009-10-26 21:27:30pitroucreate