Message 59116 - 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	gvanrossum
Recipients	christian.heimes, gvanrossum, kbk
Date	2008-01-03.00:15:00
SpamBayes Score	0.27912468
Marked as misclassified	No
Message-id	<1199319301.14.0.660468160584.issue1567@psf.upfronthosting.co.za>
In-reply-to

Content
Can you produce a version of the patch that applies cleanly to 2.6? Then we can apply it there first and merge into 3.0 later. But I wonder. It seems this changes every single call to PyImport_ImportModule() in the core to _PyImport_ImportModuleNoLock(). What's the point of the lock at that point?

Can you produce a version of the patch that applies cleanly to 2.6? Then
we can apply it there first and merge into 3.0 later.

But I wonder.  It seems this changes every single call to
PyImport_ImportModule() in the core to _PyImport_ImportModuleNoLock(). 
What's the point of the lock at that point?

History
Date	User	Action	Args
2008-01-03 00:15:01	gvanrossum	set	spambayes_score: 0.279125 -> 0.27912468 recipients: + gvanrossum, kbk, christian.heimes
2008-01-03 00:15:01	gvanrossum	set	spambayes_score: 0.279125 -> 0.279125 messageid: <1199319301.14.0.660468160584.issue1567@psf.upfronthosting.co.za>
2008-01-03 00:15:01	gvanrossum	link	issue1567 messages
2008-01-03 00:15:00	gvanrossum	create