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.

Title: Document poor interaction between multiprocessing and -m on Windows
Type: Stage: resolved
Components: Versions:
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: ncoghlan
Priority: normal Keywords:

Created on 2011-12-21 14:15 by ncoghlan, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg149988 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2011-12-21 14:15
The section of the docs should document the limitations that multiprocessing on Windows places on __main__ module invocation.

- no execution of modules inside packages with -m
- no execution of packages (since their __main__ is inside the package)
msg149991 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2011-12-21 14:32
(Actually the latter isn't true - the __main__ bypass handles that case. Since none of the code gets executed in the child process, it doesn't generally matter that __package__ isn't set properly)
msg278450 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2016-10-11 02:46
These interactions were fixed in the release where *nix multiprocessing gained the ability to mimic the Windows behaviour.
Date User Action Args
2022-04-11 14:57:24adminsetgithub: 57855
2016-10-11 02:46:57ncoghlansetstatus: open -> closed
resolution: out of date
messages: + msg278450

stage: resolved
2011-12-21 14:32:54ncoghlansetmessages: + msg149991
2011-12-21 14:15:03ncoghlancreate