[issue5906] Risk of confusion in multiprocessing module - daemonic processes
Pascal Chambon
report at bugs.python.org
Tue Jun 7 15:06:29 CEST 2011
Pascal Chambon <chambon.pascal at gmail.com> added the comment:
I've just crossed again the doc of the daemon flag (http://docs.python.org/library/multiprocessing.html), and it's still quite confusing to newcomers.
daemon
The process’s daemon flag, a Boolean value. This must be set before start() is called.
The initial value is inherited from the creating process. [1]
When a process exits, it attempts to terminate all of its daemonic child processes.
[1] this sentence is weird: since daemonic processes are not allowed to have children, isn't this flag always False in a new Process instance ?
[2] typo, it meant "all of its NON-daemonic child processes" instead, didn't it ?
----------
resolution: fixed ->
status: closed -> open
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5906>
_______________________________________
More information about the Python-bugs-list
mailing list