➜

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.

classification
Title: multiprocessing.set_start_method force argument is not documented
Type: enhancement Stage: patch review
Components: Documentation Versions: Python 3.11, Python 3.10, Python 3.9, Python 3.8, Python 3.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: John Hagen, docs@python, sam_ezeh
Priority: normal Keywords: patch

Created on 2022-03-31 17:42 by John Hagen, last changed 2022-04-11 14:59 by admin.

Pull Requests
URL Status Linked Edit
PR 32339 open sam_ezeh, 2022-04-05 19:08
Messages (2)
msg416451 - (view) Author: John Hagen (John Hagen) * Date: 2022-03-31 17:42 
multiprocessing.set_start_method() has a `force` argument that is not documented: https://docs.python.org/3.10/library/multiprocessing.html#multiprocessing.set_start_method
msg416805 - (view) Author: Sam Ezeh (sam_ezeh) * Date: 2022-04-05 19:12 
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.
History
Date User Action Args
2022-04-11 14:59:57adminsetgithub: 91340
2022-04-05 19:12:05sam_ezehsetnosy: docs@python, John Hagen, sam_ezeh
messages: + msg416805
2022-04-05 19:08:49sam_ezehsetkeywords: + patch
nosy: + sam_ezeh

pull_requests: + pull_request30395
stage: patch review
2022-03-31 17:42:20John Hagencreate