Message 110318 - 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	pitrou
Recipients	belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, pitrou
Date	2010-07-14.19:34:32
SpamBayes Score	0.0043045967
Marked as misclassified	No
Message-id	<1279136070.3128.11.camel@localhost.localdomain>
In-reply-to	<1279134751.86.0.556944373629.issue9260@psf.upfronthosting.co.za>

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. Yes but what happens if two different modules are imported from two different threads, and handled by the same loader? The loader could have global structures which rely on serialization of imports for consistency.

> 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.

Yes but what happens if two different modules are imported from two
different threads, and handled by the same loader? The loader could have
global structures which rely on serialization of imports for
consistency.

History
Date	User	Action	Args
2010-07-14 19:34:35	pitrou	set	recipients: + pitrou, gvanrossum, brett.cannon, ncoghlan, belopolsky, christian.heimes, grahamd
2010-07-14 19:34:33	pitrou	link	issue9260 messages
2010-07-14 19:34:32	pitrou	create