diff options
| author | Ask Solem <askh@opera.com> | 2010-11-09 21:52:33 +0000 |
|---|---|---|
| committer | Ask Solem <askh@opera.com> | 2010-11-09 21:52:33 +0000 |
| commit | ff7ffdd752a84395e1b10a9d2fa848d80f85c400 (patch) | |
| tree | baff494a1c1d636ee8a885ac04de3ca6697ec991 /Doc/library/multiprocessing.rst | |
| parent | 518eaa8a7676a456ef8f04a8645af28c8b1ea09c (diff) | |
| download | cpython-git-ff7ffdd752a84395e1b10a9d2fa848d80f85c400.tar.gz | |
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.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index d611278700..d7a37c3f1a 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`: |