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 brett.cannon
Recipients belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, pitrou
Date 2010-07-14.23:40:13
SpamBayes Score 0.017127626
Marked as misclassified No
Message-id <1279150814.96.0.0597715098853.issue9260@psf.upfronthosting.co.za>
In-reply-to
Content
That's my point; loaders are using the lock implicitly so that's why we don't need to worry about the global import lock just for path hooks. It seems like you are suggesting using the global import lock purely for compatibility, and what I am saying is that loaders don't care so there is no compatibility to care about. I say only use the global import lock for serializing creation.
History
Date User Action Args
2010-07-14 23:40:15brett.cannonsetrecipients: + brett.cannon, gvanrossum, ncoghlan, belopolsky, pitrou, christian.heimes, grahamd
2010-07-14 23:40:14brett.cannonsetmessageid: <1279150814.96.0.0597715098853.issue9260@psf.upfronthosting.co.za>
2010-07-14 23:40:13brett.cannonlinkissue9260 messages
2010-07-14 23:40:13brett.cannoncreate