Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document poor interaction between multiprocessing and -m on Windows #57855

Closed
ncoghlan opened this issue Dec 21, 2011 · 3 comments
Closed

Document poor interaction between multiprocessing and -m on Windows #57855

ncoghlan opened this issue Dec 21, 2011 · 3 comments

Comments

@ncoghlan
Copy link
Contributor

BPO 13646
Nosy @ncoghlan

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-10-11.02:46:57.873>
created_at = <Date 2011-12-21.14:15:03.875>
labels = []
title = 'Document poor interaction between multiprocessing and -m on Windows'
updated_at = <Date 2016-10-11.02:46:57.871>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2016-10-11.02:46:57.871>
actor = 'ncoghlan'
assignee = 'none'
closed = True
closed_date = <Date 2016-10-11.02:46:57.873>
closer = 'ncoghlan'
components = []
creation = <Date 2011-12-21.14:15:03.875>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 13646
keywords = []
message_count = 3.0
messages = ['149988', '149991', '278450']
nosy_count = 1.0
nosy_names = ['ncoghlan']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue13646'
versions = []

@ncoghlan
Copy link
Contributor Author

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)

@ncoghlan
Copy link
Contributor Author

(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)

@ncoghlan
Copy link
Contributor Author

These interactions were fixed in the release where *nix multiprocessing gained the ability to mimic the Windows behaviour.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant