summaryrefslogtreecommitdiffstats
path: root/Doc/library/multiprocessing.rst
diff options
context:
space:
mode:
authorAsk Solem <askh@opera.com>2010-11-09 21:52:33 (GMT)
committerAsk Solem <askh@opera.com>2010-11-09 21:52:33 (GMT)
commitff7ffdd752a84395e1b10a9d2fa848d80f85c400 (patch)
treebaff494a1c1d636ee8a885ac04de3ca6697ec991 /Doc/library/multiprocessing.rst
parent518eaa8a7676a456ef8f04a8645af28c8b1ea09c (diff)
downloadcpython-ff7ffdd752a84395e1b10a9d2fa848d80f85c400.zip
cpython-ff7ffdd752a84395e1b10a9d2fa848d80f85c400.tar.gz
cpython-ff7ffdd752a84395e1b10a9d2fa848d80f85c400.tar.bz2
Issue #8028: multiprocessing: Documented that ``Process.terminate``
is only intented for use by the parent process.
Diffstat (limited to 'Doc/library/multiprocessing.rst')
-rw-r--r--Doc/library/multiprocessing.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index d611278..d7a37c3 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -422,9 +422,9 @@ The :mod:`multiprocessing` package mostly replicates the API of the
acquired a lock or semaphore etc. then terminating it is liable to
cause other processes to deadlock.
- Note that the :meth:`start`, :meth:`join`, :meth:`is_alive` and
- :attr:`exit_code` methods should only be called by the process that created
- the process object.
+ Note that the :meth:`start`, :meth:`join`, :meth:`is_alive`,
+ :meth:`terminate` and :attr:`exit_code` methods should only be called by
+ the process that created the process object.
Example usage of some of the methods of :class:`Process`: