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.19:12:30
SpamBayes Score 0.046534978
Marked as misclassified No
Message-id <1279134751.86.0.556944373629.issue9260@psf.upfronthosting.co.za>
In-reply-to
Content
So I say we don't worry about loaders being thread-safe. If __import__ handles the locking for a specific module then it will hold the lock on behalf of the loader. Now if someone decides to call load_module on their own, that's there business, but they should be aware of what could happen if they do that without acquiring the lock themselves. Otherwise we just make sure to provide a context manager that takes the name of the module and people can use that when they make their call to loader.load_module.
History
Date User Action Args
2010-07-14 19:12:32brett.cannonsetrecipients: + brett.cannon, gvanrossum, ncoghlan, belopolsky, pitrou, christian.heimes, grahamd
2010-07-14 19:12:31brett.cannonsetmessageid: <1279134751.86.0.556944373629.issue9260@psf.upfronthosting.co.za>
2010-07-14 19:12:30brett.cannonlinkissue9260 messages
2010-07-14 19:12:30brett.cannoncreate