Set multiprocessing start method to fork
#9793
Merged
+4
−22
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.
Subject: Set multiprocessing start method to
fork
Feature or Bugfix
Purpose
Explicitly set the multiprocessing start method to
fork
since the code depends on this behavior.Detail
Since Python 3.8, the default start method was changed to
spawn
on macOS, which is incompatible with how Sphinx handles parallelization. The change was made in macOS not due to a new security concern but because Apple decided to prevent potential problems with calling something betweenfork()
andexec()
by failing early. This problem is not unique to macOS or even Python, and depends on the implementation.From looking at the use of
multiprocessing
in Sphinx, I don't believe this will cause issues on macOS.Relates