[3.14] gh-149857: Clarify multiprocessing Process argument wording (GH-149919) (...

gh-149857: Clarify multiprocessing Process argument wording (GH-149919)

Use consistent 'picklable' wording
(cherry picked from commit 1bab6c919212cbac9be9e37bbd4d85865051f17f)

Co-authored-by: Mani Salahmand <78011313+ManiSalahmand@users.noreply.github.com>

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index cc32a76c58453d6a4f7ab7a8fce2c878d6a700ff..d3350217be80a6d2e8e9f956bcf703abd053416b 100644 (file)
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -100,10 +100,10 @@ To show the individual process IDs involved, here is an expanded example::
 For an explanation of why the ``if __name__ == '__main__'`` part is
 necessary, see :ref:`multiprocessing-programming`.
 
-The arguments to :class:`Process` usually need to be unpickleable from within
-the child process. If you tried typing the above example directly into a REPL it
-could lead to an :exc:`AttributeError` in the child process trying to locate the
-*f* function in the ``__main__`` module.
+The arguments to :class:`Process` usually need to be picklable so they can be
+passed to the child process. If you tried typing the above example directly
+into a REPL it could lead to an :exc:`AttributeError` in the child process
+trying to locate the *f* function in the ``__main__`` module.
 
 
 .. _multiprocessing-start-methods: