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

is only intented for use by the parent process.

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index d6112787005c146eb2b59ee7af3acf8503f1ba1d..d7a37c3f1ae49946efa45ec21457a608c15a8100 100644 (file)
--- 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`:
 

diff --git a/Misc/NEWS b/Misc/NEWS
index 365b9cb99443ef7a7cfecc4292fdda9299cc3aa4..9e3b4580b95a5f5c589dedf5d664acafa5a91ea0 100644 (file)
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -2879,6 +2879,9 @@ Build
 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
   can lead to deadlocks.