Antoine Pitrou writes:
> Le Wed, 14 Aug 2013 14:17:59 +0900, Arnaud Fontaine
> a écrit :
>> From my understanding of import.c source code, until something is
>> added to sys.modules or the code loaded, there should be no
>> side-effect to releasing the lock, right
Antoine Pitrou writes:
> Le Tue, 13 Aug 2013 17:28:42 +0900, Arnaud Fontaine
> a écrit :
>> Yes. Actually, I was thinking about implementing something similar to
>> what has been done in Python 3.3 but for Python 2.7 with a
>> corser-grain lock. From my understandin
Antoine Pitrou writes:
> On Tue, 13 Aug 2013 11:06:51 +0900 Arnaud Fontaine
> wrote:
>> I suggested the same in my initial email, but I was wondering if there
>> could be any issue by releasing the lock in find_module()/load_module()
>> until the module is actua
Brett Cannon writes:
> On Mon, Aug 12, 2013 at 5:12 AM, Arnaud Fontaine wrote:
>> Yes, I saw the bug report and its patch implementing the import lock per
>> module (mentioned in my initial email) and watched the presentation by
>> Brett Cannon (BTW, I could not find the dia
Hi,
Armin Rigo writes:
> On Mon, Aug 12, 2013 at 9:39 AM, Arnaud Fontaine
> wrote:
>> Thread 1 is trying to import a module 'foo.bar' (where 'foo' is a
>> package containing dynamic modules) handled by Import Hooks I
>> implemented, so imp
unfortunately, Zope 2 does not support
it. What about the other solution I suggested though?
Regards,
--
Arnaud Fontaine
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mai
uld not have nasty
side-effects, any thoughts about that?
* Fix the ZODB code to not avoid import but to me this seems like a
dirty hack because it could happen again and I would prefer to fix
this issue once and for all.
Any thoughts or suggestion welcome, thanks!
Regards,
Arnaud Fontain
