Skip to content

gh-84559: Remove the new multiprocessing warning, too disruptive. #101551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gpshead merged 3 commits into from
Feb 3, 2023
Merged

gh-84559: Remove the new multiprocessing warning, too disruptive. #101551

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
20cec00
gh-84559: Remove the new mp warning, too disruptive.
gpshead Feb 3, 2023
aa42413
doc section indentation fix
gpshead Feb 3, 2023
c576f05
docs: missing word
gpshead Feb 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
doc section indentation fix
  • Loading branch information
@gpshead
gpshead authored Feb 3, 2023
commit aa42413b33629198c0b10f7deb230d638e0024ee
14 changes: 7 additions & 7 deletions Doc/library/concurrent.futures.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,13 +281,13 @@ to a :class:`ProcessPoolExecutor` will result in deadlock.

Added the *initializer* and *initargs* arguments.

.. note::
The default :mod:`multiprocessing` start method
(see :ref:`multiprocessing-start-methods`) will change away from
*fork* in Python 3.14. Code that requires *fork* be used for their
:class:`ProcessPoolExecutor` should explicitly specify that by
passing a ``mp_context=multiprocessing.get_context("fork")``
parameter.
.. note::
The default :mod:`multiprocessing` start method
(see :ref:`multiprocessing-start-methods`) will change away from
*fork* in Python 3.14. Code that requires *fork* be used for their
:class:`ProcessPoolExecutor` should explicitly specify that by
passing a ``mp_context=multiprocessing.get_context("fork")``
parameter.

.. versionchanged:: 3.11
The *max_tasks_per_child* argument was added to allow users to
Expand Down