Alex Roitman <rsh...@gmail.com> added the comment:

1. If fork should not be called during import, it could raise an exception when 
invoked from import.  But it does not.  Is that a bug then?  BTW, fork during 
import worked with python 2.4 just fine.

2. The whole issue7242 was devoted to work out import locks during forking. 5 
months ago r78527 was committed to to just that (although it is not perfect). 
If this is not the proper use case then had it been done in error?

3. belopolsky: Thanks for the advice to use the mailing list.  I'd appreciate 
it if instead you refrained from publishing my email address on this page.

----------
title: imporing a module that executes fork() raises RuntimeError -> importing 
a module that executes fork() raises RuntimeError

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9573>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to