[issue47184] multiprocessing.set_start_method force argument is not documented
New submission from John Hagen <johnthagen@gmail.com>: multiprocessing.set_start_method() has a `force` argument that is not documented: https://docs.python.org/3.10/library/multiprocessing.html#multiprocessing.se... ---------- assignee: docs@python components: Documentation messages: 416451 nosy: John Hagen, docs@python priority: normal severity: normal status: open title: multiprocessing.set_start_method force argument is not documented type: enhancement versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue47184> _______________________________________
Change by Sam Ezeh <sam.z.ezeh@gmail.com>: ---------- keywords: +patch nosy: +sam_ezeh nosy_count: 2.0 -> 3.0 pull_requests: +30395 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32339 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue47184> _______________________________________
Sam Ezeh <sam.z.ezeh@gmail.com> added the comment: It's quite weird, the documentation says set_start_method "should not be used more than once in the program" twice. The source code also contains the following line ``` # Type of default context -- underlying context can be set at most once ``` I'm not too familiar with the multiprocessing library but with the force parameter set to True, I don't understand why that can't happen. If there's a specific reason, maybe that should be documented too. ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue47184> _______________________________________
participants (2)
-
John Hagen -
Sam Ezeh