docs: document multiprocessing fork warning workaround for #1186#1336
Open
golikovichev wants to merge 1 commit into
Open
docs: document multiprocessing fork warning workaround for #1186#1336golikovichev wants to merge 1 commit into
golikovichev wants to merge 1 commit into
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
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.
This adds a short docs section explaining the multiprocessing fork warning that surfaces in #1186 and pointing readers at the spawn-context workaround that @RonnyPfannschmidt has suggested in the thread.
The intent is to make the workaround discoverable from the project docs rather than only from the issue comments, while the upstream execnet#336 experiment is still in progress. Once that lands and the warning stops appearing for the fork case, this section can either be trimmed to a note about historical 3.x behaviour or removed entirely.
Closes nothing. The issue should stay open until the execnet-side fix lands.
Links:
The new section is added at the end of docs/known-limitations.rst since that page already lists xdist quirks with workarounds. If you would prefer it under a different page (e.g. a future FAQ), let me know and I will move it.