New submission from Antoine Pitrou:
It may happen that the forkserver process dies (for example if SIGINT is
received because the user pressed Ctrl-C) while the parent process is still
alive. In that case, if the parent tries to create a new Process instance, an
exception is received.
The exception looks like this:
File "/xxx/lib/python3.5/multiprocessing/popen_forkserver.py", line 52, in
_launch
self.sentinel, w = forkserver.connect_to_new_process(self._fds)
File "/xxx/lib/python3.5/multiprocessing/forkserver.py", line 66, in
connect_to_new_process
client.connect(self._forkserver_address)
ConnectionRefusedError: [Errno 111] Connection refused
----------
components: Library (Lib)
messages: 301027
nosy: pitrou
priority: normal
severity: normal
stage: needs patch
status: open
title: forkserver process isn't re-launched if it died
type: behavior
versions: Python 3.6, Python 3.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue31308>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
