New submission from Colin <cjphl...@gmail.com>:

The docstring on Forkserver.ensure_running states that a child process will use 
the forkserver process started by its parent:

"""
Make sure that a fork server is running.

This can be called from any process.  Note that usually a child
process will just reuse the forkserver started by its parent, so
ensure_running() will do nothing.
"""

Link to definition: 
https://github.com/python/cpython/blob/master/Lib/multiprocessing/forkserver.py#L105

That is not the behavior that I am seeing, however. I'm seeing each child (that 
start a process itself) will first spawn a *new* forkserver.

----------
components: Library (Lib)
files: test.py
messages: 379851
nosy: cchomey
priority: normal
severity: normal
status: open
title: forkserver not reused in child processes
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file49547/test.py

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

Reply via email to