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
Update multiprocessing docs re: freeze_support #49751
Comments
Indicate in docs whether freeze_support() can be called without issues |
I think that question is covered by "If the module is being run normally by the Python interpreter then freeze_support() has no effect." Jesse, do you think anything more is needed, like '(on any platform)' after 'interpreter', or should be close this? |
Hello, Regards, |
I’m assuming this is a feature new in 2.7 and 3.2, please add 3.1 if this is wrong. |
Sorry Éric, I don't get it: do you mean that the fact that "freeze_support() can be called without issues on Unix or OS X" is a new feature? or I misread it completely? |
Rephrased: Is this relevant for 3.1? (Bug and doc fixes go into 3.2, 3.1 and 2.7, but here only 3.2 and 2.7 are selected, so I asked if the bugfix/new feature/behavior in question was something new in 3.2 and thus not in 3.1.) |
Hi everyone! Patch attached. |
Thank you, Winterflower, for the nudge to see this set right. In truth, invoking multiprocessing.freeze_support() has zero effect on platforms other than Windows. This should be reflected in the 2.7 docs as well as the 3.x docs that are still actively being updated. Attached are 2 patches -- they should be cleanly applied to the 2.7, 3.5, and default (3.6) branches. This change clarifies the last line of existing documentation around freeze_support() as well as clearly states what I mentioned above. |
Patch review: 3.X patch: Applied to branch 3.5. Docs build passes, doc layout has not been broken. 2.X patch: Comments on the contents of the patch: if the module is being run normally by the Python interpreter on Windows (the program has not been frozen) For a newbie Python user it might not be entirely clear what 'run normally by the Python interpreter' means. Perhaps it would be nice to add a clarifying clause if the module is being run normally by the Python interpreter ( for example, by running python <filename.py> from the command prompt) on Windows (the program has not been frozen) or something similar. |
New changeset f08d4712a055 by Berker Peksag in branch '3.5': New changeset 2902f32d1ae9 by Berker Peksag in branch 'default': |
New changeset 8b20a606ecde by Berker Peksag in branch '2.7': |
Thanks Davin and Camilla. |
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: