gh-125714: Doc: Explain that multiprocessing only supports unpicklable functions through the fork method#125750
gh-125714: Doc: Explain that multiprocessing only supports unpicklable functions through the fork method#125750progval wants to merge 7 commits intopython:mainfrom
Conversation
… through the fork method In multiprocessing and concurrent.futures's documentations, as well as the release notes for Python 3.14. This moves the paragraph in 3.14's release notes from the deprecations section to 'Porting to Python 3.14' because it is a breaking change, which follows a deprecation in Python 3.12. This explicitly mentions `PicklingError` in this section, so it is easy to find for somehow who gets the error and searches its name through the page.
|
The following commit authors need to sign the Contributor License Agreement: Click the button to sign: |
|
Is it possible to skip the CLA for such a small change? |
|
You must sign the CLA, which gives us permission to distribute your work. |
Co-authored-by: Jelle Zijlstra <[email protected]>
|
I am afraid you will have to sign the CLA. |
I already did by submitting this PR after accepting Github's terms of service:
Nonetheless, I'm fine with the CLA on principle, but I'm not willing to give out the personal info the cla-bot or the form are asking for. |
5 participants
In multiprocessing and concurrent.futures's documentations, as well as the release notes for Python 3.14.
This moves the paragraph in 3.14's release notes from the deprecations section to 'Porting to Python 3.14' because it is a breaking change, which follows a deprecation in Python 3.12.
This explicitly mentions
PicklingErrorin this section, so it is easy to find for somehow who gets the error and searches its name through the page._pickle.PicklingErroron 3.14.0a1+ where it didn't before due to the start method change from fork to forkserver #125714📚 Documentation preview 📚: https://cpython-previews--125750.org.readthedocs.build/