[issue21998] asyncio: a new self-pipe should be created in the child process after fork
Martin Richard
report at bugs.python.org
Mon Dec 1 10:23:06 CET 2014
Martin Richard added the comment:
Guido,
Currently in my program, I manually remove and then re-adds the reader to the loop in the parent process right after the fork(). I also considered a dirty monkey-patching of remove_reader() and remove_writer() which would act as the original versions but without removing the fds from the epoll object (ensuring I don't get bitten by the same behavior for an other fd).
The easiest fix, I think, is indeed to close the selector without unregistering the fds, but I don't know if doing so would have undesired side effects on an other platform than Linux (resources leak, or the close call failing maybe).
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21998>
_______________________________________
More information about the Python-bugs-list
mailing list