8000 [3.12] gh-115664: Fix versionadded and versionchanged directives in multiprocessing.rst (GH-115665) by miss-islington · Pull Request #115677 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

[3.12] gh-115664: Fix versionadded and versionchanged directives in multiprocessing.rst (GH-115665) #115677

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
merged 1 commit into from
Feb 19, 2024
Merged

[3.12] gh-115664: Fix versionadded and versionchanged directives in multiprocessing.rst (GH-115665) #115677

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8000
Diff view
29 changes: 14 additions & 15 deletions Doc/library/multiprocessing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,18 +150,18 @@ to start a process. These *start methods* are
over Unix pipes such as Linux.


.. versionchanged:: 3.8

On macOS, the *spawn* start method is now the default. The *fork* start
method should be considered unsafe as it can lead to crashes of the
subprocess as macOS system libraries may start threads. See :issue:`33725`.

.. versionchanged:: 3.4
*spawn* added on all POSIX platforms, and *forkserver* added for
some POSIX platforms.
Child processes no longer inherit all of the parents inheritable
handles on Windows.

.. versionchanged:: 3.8

On macOS, the *spawn* start method is now the default. The *fork* start
method should be considered unsafe as it can lead to crashes of the
subprocess as macOS system libraries may start threads. See :issue:`33725`.

On POSIX using the *spawn* or *forkserver* start methods will also
start a *resource tracker* process which tracks the unlinked named
system resources (such as named semaphores or
Expand Down Expand Up @@ -519,7 +519,7 @@ The :mod:`multiprocessing` package mostly replicates the API of the
to the process.

.. versionchanged:: 3.3
Added the *daemon* argument.
Added the *daemon* parameter.

.. method:: run()

Expand Down Expand Up @@ -1238,8 +1238,7 @@ Connection objects are usually created using
Connection objects themselves can now be transferred between processes
using :meth:`Connection.send` and :meth:`Connection.recv`.

.. versionadded:: 3.3
Connection objects now support the context management protocol -- see
Connection objects also now support the context management protocol -- see
:ref:`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the
connection object, and :meth:`~contextmanager.__exit__` calls :meth:`close`.

Expand Down Expand Up @@ -2243,11 +2242,11 @@ with the :class:`Pool` class.
as CPython does not assure that the finalizer of the pool will be called
(see :meth:`object.__del__` for more information).

.. versionadded:: 3.2
*maxtasksperchild*
.. versionchanged:: 3.2
Added the *maxtasksperchild* parameter.

.. versionadded:: 3.4
*context*
.. versionchanged:: 3.4
Added the *context* parameter.

.. note::

Expand Down Expand Up @@ -2369,7 +2368,7 @@ with the :class:`Pool` class.
Wait for the worker processes to exit. One must call :meth:`close` or
:meth:`terminate` before using :meth:`join`.

.. versionadded:: 3.3
.. versionchanged:: 3.3
Pool objects now support the context management protocol -- see
:ref:`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the
pool object, and :meth:`~contextmanager.__exit__` calls :meth:`terminate`.
Expand Down Expand Up @@ -2538,7 +2537,7 @@ multiple connections at the same time.
The address from which the last accepted connection came. If this is
unavailable then it is ``None``.

.. versionadded:: 3.3
.. versionchanged:: 3.3
Listener objects now support the context management protocol -- see
:ref:`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the
listener object, and :meth:`~contextmanager.__exit__` calls :meth:`close`.
Expand Down
0