Explicitly set multiprocessing start method to fork for OSX support #182
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
This fixes an issue preventing pyModeS from being usable on OSX. The root cause of the issue is that the default start method for multiprocessing on OSX is
spawnwhich is not compatible with pyModeS. Additionally, as of Python 3.14forkmust be specified explicitly. See: https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methodsThere's probably a better way to clean this up however this is the simplest fix for now.
Testing Done
Before:
After
