[Python-checkins] r86376 - in python/branches/py3k: Doc/library/multiprocessing.rst Misc/NEWS
python-checkins at python.org
Tue Nov 9 22:52:33 CET 2010
Date: Tue Nov 9 22:52:33 2010
New Revision: 86376
Issue #8028: multiprocessing: Documented that ``Process.terminate``
is only intented for use by the parent process.
--- python/branches/py3k/Doc/library/multiprocessing.rst (original)
+++ python/branches/py3k/Doc/library/multiprocessing.rst Tue Nov 9 22:52:33 2010
@@ -422,9 +422,9 @@
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`:
--- python/branches/py3k/Misc/NEWS (original)
+++ python/branches/py3k/Misc/NEWS Tue Nov 9 22:52:33 2010
@@ -2879,6 +2879,9 @@
+- Issue #8028: ``terminate()`` was missing from the list of
+ ``multiprocessing.Process`` methods only intended for use by the parent.
- Issue #7707: Document that ``multiprocessing.Queue`` operations during import
can lead to deadlocks.
More information about the Python-checkins