➜
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.
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) *  |
Date: 2011-12-21 14:15 | |
The http://docs.python.org/library/multiprocessing#windows 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) * |
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) * |
Date: 2016-10-11 02:46 | |
These interactions were fixed in the release where *nix multiprocessing gained the ability to mimic the Windows behaviour. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:24 | admin | set | github: 57855 |
| 2016-10-11 02:46:57 | ncoghlan | set | status: open -> closed resolution: out of date messages: + msg278450 stage: resolved |
| 2011-12-21 14:32:54 | ncoghlan | set | messages: + msg149991 |
| 2011-12-21 14:15:03 | ncoghlan | create | |