From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Sun, 31 May 2026 04:22:18 +0000 (+0200)
Subject: [3.13] gh-149857: Clarify multiprocessing Process argument wording (GH-149919) (... 
X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=42f3fbf5951c07ff08c5e6fc8b83a2763cbda414;p=thirdparty%2FPython%2Fcpython.git

[3.13] gh-149857: Clarify multiprocessing Process argument wording (GH-149919) (#149935)

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 eab6bbecb468..108fd4536da0 100644
--- 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: