[issue26732] multiprocessing sentinel resource leak
Kevin Quick added the comment: Thank you for the fix, pitrou! Regarding your comment regarding the behavior being expected with the "fork" method, I would suggest a documentation modification in the description of the fork method to add something to the effect of "All resources of the parent are inherited by the child process; this includes the ability of later children to act as the parent of earlier children via the various functions in this package." -- ___ Python tracker <http://bugs.python.org/issue26732> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26732] multiprocessing sentinel resource leak
Kevin Quick added the comment: Hi Antoine, > ... an implementation detail rather than a documented feature I understand your desire, but this is a leaky abstraction and I would still suggest that it should be more clear that the fork method will inherit *all* resources from the parent, including multiprocessing internal resources related to other processes. This is potentially important if there are (a) large numbers of processes to be created and (b) for security aspects. Regards, Kevin -- ___ Python tracker <http://bugs.python.org/issue26732> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6638] optparse parse_args argument references wrong
New submission from Kevin Quick : In optparse description of "16.4.3.7. Parsing arguments" (http:// docs.python.org/library/optparse.html#parsing-arguments) the keyword argument to parse_args is "values=None" but in the description of the "options" return value and in the second sentence of the "Most common usage..." paragraph following, it is referred to as the "options" argument. -- assignee: georg.brandl components: Documentation messages: 91247 nosy: georg.brandl, kq1quick severity: normal status: open title: optparse parse_args argument references wrong type: resource usage versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue6638> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26732] multiprocessing sentinel resource leak
New submission from Kevin Quick: The sentinel creates a named pipe, but the parent's end of the pipe is inherited by subsequently created children. import multiprocessing,signal,sys def sproc(x): signal.pause() for each in range(int(sys.argv[1])): multiprocessing.Process(target=sproc, args=(each,)).start() signal.pause() Running the above on Linux with varying numbers of child processes (expressed as the argument to the above) and using techniques like "$ sudo ls /proc//fd" it is possible to see an ever growing number of pipe connections for subsequent children. -- components: Library (Lib) messages: 263153 nosy: quick-b priority: normal severity: normal status: open title: multiprocessing sentinel resource leak type: resource usage versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue26732> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26732] multiprocessing sentinel resource leak
Kevin Quick added the comment: (Sorry, an unnamed pipe, but a pipe nonetheless.) -- ___ Python tracker <http://bugs.python.org/issue26732> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
