On Fri, 22 Jul 2011 21:29:23 +1200
Greg Ewing <greg.ew...@canterbury.ac.nz> wrote:
>
> This whole episode seems to have resulted from a collision
> between two rather obscure things: that import statements
> involve locking things, and that some fairly innocuous
> looking calls, such as s.encode('ascii'), can trigger an
> import.
Indeed.
> I'm wondering whether anything can be done to make problems
> like this less likely to occur, or at least to make the
> cause more readily apparent. One shouldn't really have to
> use gdb to track down bugs in Python code.
See http://bugs.python.org/issue9260
There's a patch there but it needs additional sophistication to remove
deadlocks when doing concurrent circular imports.
Regards
Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
