[3.11] gh-90876: Restore the ability to import multiprocessing when sys.executable
is None
(GH-106464)
#106495
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.
Prevent
multiprocessing.spawn
from failing to import in environmentswhere
sys.executable
isNone
. This regressed in 3.11 with the additionof support for path-like objects in multiprocessing.
Adds a test decorator to have tests only run when part of test_multiprocessing_spawn to
_test_multiprocessing.py
so we can start to avoid re-running the same not-global-state specific test in all 3 modes when there is no need.(cherry picked from commit c60df36)
Co-authored-by: Gregory P. Smith [email protected]