gh-140814: Fix call order in multiprocessing example #144606
Closed
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Swaps the order of
set_start_method()andfreeze_support()in the "Safe importing of main module" example in the multiprocessing docs.freeze_support()internally callsget_start_method(), which sets_actual_contexton the default context (Lib/multiprocessing/context.py:240-244). A subsequentset_start_method('spawn')then raisesRuntimeError('context has already been set')because_actual_contextis no longerNone(context.py:249).Calling
set_start_method()first avoids this, sincefreeze_support()will then use the already-configured spawn context.Test plan
make -C Doc checkpassesmake -C Doc htmlpasses (no warnings)Lib/multiprocessing/context.pylines 144-150, 240-254🤖 Generated with Claude Code
📚 Documentation preview 📚: https://cpython-previews--144606.org.readthedocs.build/