Skip to content

Commit 1bab6c9

Browse files
gh-149857: Clarify multiprocessing Process argument wording (GH-149919)
Use consistent 'picklable' wording
1 parent 5f8d9d3 commit 1bab6c9

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

Doc/library/multiprocessing.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -100,10 +100,10 @@ To show the individual process IDs involved, here is an expanded example::
100100
For an explanation of why the ``if __name__ == '__main__'`` part is
101101
necessary, see :ref:`multiprocessing-programming`.
102102

103-
The arguments to :class:`Process` usually need to be unpickleable from within
104-
the child process. If you tried typing the above example directly into a REPL it
105-
could lead to an :exc:`AttributeError` in the child process trying to locate the
106-
*f* function in the ``__main__`` module.
103+
The arguments to :class:`Process` usually need to be picklable so they can be
104+
passed to the child process. If you tried typing the above example directly
105+
into a REPL it could lead to an :exc:`AttributeError` in the child process
106+
trying to locate the *f* function in the ``__main__`` module.
107107

108108

109109
.. _multiprocessing-start-methods:

0 commit comments

Comments
 (0)