Neal Norwitz wrote: >> As I said: I doubt it is the right thing to do. Instead, the lock >> should get released in the child process if it is held at the >> point of the fork. >> > I'm not sure if this bug can be reproduced now, but the comment in > warnings.py points to: > > http://python.org/sf/683658 > > I didn't investigate it further. That might allow someone to create a > reproducible test case.
That's a different problem, though. Here, the main thread waits for a child *thread* while holding the import lock. I don't quite understand the test case given, and I can't make it deadlock anymore (probably because of Just's fix). Regards, Martin _______________________________________________ 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
