Avoid the multiprocessing forkserver method #343
+13
−2
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.
What's new in Python 3.14 states:
The default start method changed from fork to forkserver on platforms other than macOS and Windows where it was already spawn.
If the threading incompatible fork method is required, you must explicitly request it via a context from multiprocessing.get_context() (preferred) or change the default via
multiprocessing.set_start_method().
Source:
https://docs.python.org/dev/whatsnew/3.14.html#whatsnew314-multiprocessing-start-method
This change is incompatible with the current test settings. The patch is backwards compatible.
You can see the build results in my testing Fedora Copr where I try to build satyr with Python 3.14.0 - the latest build, containing this commit, is successful: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/satyr/