https://github.com/python/cpython/commit/c39baf15c5b8b38402976abae873578ab7741156
commit: c39baf15c5b8b38402976abae873578ab7741156
branch: 3.11
author: Serhiy Storchaka <[email protected]>
committer: serhiy-storchaka <[email protected]>
date: 2024-02-19T20:52:17+02:00
summary:
[3.11] gh-115664: Fix versionadded and versionchanged directives in
multiprocessing.rst (GH-115665) (GH-115682)
(cherry picked from commit 8f602981ba95273f036968cfc5ac28fdcd1808fa)
files:
M Doc/library/multiprocessing.rst
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 21e69b24faedab..ffd690148f19b6 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -137,19 +137,19 @@ to start a process. These *start methods* are
Available on Unix platforms which support passing file descriptors
over Unix pipes.
-.. 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. See :issue:`33725`.
-
.. versionchanged:: 3.4
*spawn* added on all Unix platforms, and *forkserver* added for
some Unix platforms.
Child processes no longer inherit all of the parents inheritable
handles on Windows.
-On Unix using the *spawn* or *forkserver* start methods will also
+.. 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
:class:`~multiprocessing.shared_memory.SharedMemory` objects) created
@@ -506,7 +506,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()
@@ -1208,8 +1208,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`.
@@ -2212,11 +2211,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::
@@ -2338,7 +2337,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`.
@@ -2507,7 +2506,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`.
_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-checkins.python.org/
Member address: [email protected]
