Nick Coghlan added the comment:
These interactions were fixed in the release where *nix multiprocessing gained
the ability to mimic the Windows behaviour.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<
Nick Coghlan added the comment:
(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)
--
___
Python track
New submission from Nick Coghlan :
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 (
