1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Issue #8028: multiprocessing: Documented that `Process.terminate`

Browse Source 
is only intented for use by the parent process.
This commit is contained in:
Ask Solem 2010-11-09 21:52:33 +00:00
parent 518eaa8a76
commit ff7ffdd752
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Doc/library/multiprocessing.rst
View File

@ -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 acquired a lock or semaphore etc. then terminating it is liable to
cause other processes to deadlock. cause other processes to deadlock.
Note that the :meth:`start`, :meth:`join`, :meth:`is_alive` and Note that the :meth:`start`, :meth:`join`, :meth:`is_alive`,
:attr:`exit_code` methods should only be called by the process that created :meth:`terminate` and :attr:`exit_code` methods should only be called by
the process object. the process that created the process object.
Example usage of some of the methods of :class:`Process`: Example usage of some of the methods of :class:`Process`:

3
Misc/NEWS
View File

@ -2879,6 +2879,9 @@ Build
Documentation Documentation
------------- -------------
- 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 - Issue #7707: Document that ``multiprocessing.Queue`` operations during import
can lead to deadlocks. can lead to deadlocks.