Message 94509 - Python tracker

➜

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	rbcollins
Recipients	barry, pitrou, rbcollins, statik
Date	2009-10-26.21:15:13
SpamBayes Score	0.0010357947
Marked as misclassified	No
Message-id	<1256591705.7720.4.camel@lifeless-64>
In-reply-to	<[email protected]>

Content
On Mon, 2009-10-26 at 19:23 +0000, Antoine Pitrou wrote: > Antoine Pitrou <[email protected]> added the comment: > > Here is a patch. Looks fine to me assuming that the locking functions can be used outside the GIL. 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. -Rob

On Mon, 2009-10-26 at 19:23 +0000, Antoine Pitrou wrote:
> Antoine Pitrou <[email protected]> added the comment:
> 
> Here is a patch.

Looks fine to me assuming that the locking functions can be used outside
the GIL.

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.

-Rob

History
Date	User	Action	Args
2009-10-26 21:15:15	rbcollins	set	recipients: + rbcollins, barry, pitrou, statik
2009-10-26 21:15:13	rbcollins	link	issue7205 messages
2009-10-26 21:15:13	rbcollins	create