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-15.11:32:45
SpamBayes Score 0.0231363
Marked as misclassified No
Message-id <1279193563.3149.3.camel@localhost.localdomain>
In-reply-to <>
> 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.

What is your take on the threadimp2.patch in issue9251?
Date User Action Args
2010-07-15 11:32:47pitrousetrecipients: + pitrou, gvanrossum, brett.cannon, ncoghlan, belopolsky, christian.heimes, grahamd
2010-07-15 11:32:46pitroulinkissue9260 messages
2010-07-15 11:32:45pitroucreate