This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pakal
Recipients jnoller, mallyvai, pakal
Date 2011-06-07.13:06:28
SpamBayes Score 2.006387e-05
Marked as misclassified No
Message-id <1307451989.49.0.0517237731357.issue5906@psf.upfronthosting.co.za>
In-reply-to
Content
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 ?
History
Date User Action Args
2011-06-07 13:06:29pakalsetrecipients: + pakal, jnoller, mallyvai
2011-06-07 13:06:29pakalsetmessageid: <1307451989.49.0.0517237731357.issue5906@psf.upfronthosting.co.za>
2011-06-07 13:06:28pakallinkissue5906 messages
2011-06-07 13:06:28pakalcreate