Message 110357 - Python tracker

Message110357

Author	pitrou
Recipients	belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, pitrou
Date	2010-07-15.11:32:45
SpamBayes Score	0.02313632
Marked as misclassified	No
Message-id	<1279193563.3149.3.camel@localhost.localdomain>
In-reply-to	<1279150814.96.0.0597715098853.issue9260@psf.upfronthosting.co.za>

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. What is your take on the threadimp2.patch in issue9251?

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.

What is your take on the threadimp2.patch in issue9251?

History
Date	User	Action	Args
2010-07-15 11:32:47	pitrou	set	recipients: + pitrou, gvanrossum, brett.cannon, ncoghlan, belopolsky, christian.heimes, grahamd
2010-07-15 11:32:46	pitrou	link	issue9260 messages
2010-07-15 11:32:45	pitrou	create