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 ncoghlan
Recipients Alex.Roitman, barry, brett.cannon, eric.araujo, gregory.p.smith, ncoghlan, r.david.murray
Date 2010-08-17.21:25:42
SpamBayes Score 3.6868897e-11
Marked as misclassified No
Message-id <1282080344.53.0.274205234364.issue9573@psf.upfronthosting.co.za>
In-reply-to
Content
On further further reflection - I'm back to thinking my patch is correct. With the way fork is now implemented, the forking thread *always* holds the import lock, so the assumption in my patch regarding the meaning of the nesting level is correct.

It could use a comment in _PyImport_ReInitLock to better explain that, though.

Unless there are any objections, I'll apply the fix to 2.7, 3.1 and 3.2.

2.6 is out of luck though (as per Barry's comment). I'll do a doc change for that, but I can't promise I'll get to it before the binary releases go out.
History
Date User Action Args
2010-08-17 21:25:44ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, gregory.p.smith, eric.araujo, r.david.murray, Alex.Roitman
2010-08-17 21:25:44ncoghlansetmessageid: <1282080344.53.0.274205234364.issue9573@psf.upfronthosting.co.za>
2010-08-17 21:25:43ncoghlanlinkissue9573 messages
2010-08-17 21:25:42ncoghlancreate