[issue22087] _UnixDefaultEventLoopPolicy should either create a new loop or explicilty fail when get_event_loop() is called from a multiprocessing child process
Guido van Rossum
report at bugs.python.org
Sat Jul 26 21:55:30 CEST 2014
Guido van Rossum added the comment:
Good point. Asyncio definitely should not share event loops across forked processes. However, I don't like the dependency on multiprocessing (even though it's in the stdlib) -- can't the policy just use os.getpid()?
Also, I've got a feeling that maybe the pid should be part of the policy state instead of the loop state? The policy could just reset self._local when the pid doesn't match.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22087>
_______________________________________
More information about the Python-bugs-list
mailing list