diff options
| author | Joe DeCapo <679017+JrGoodle@users.noreply.github.com> | 2020-05-19 14:37:09 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-19 14:37:09 (GMT) |
| commit | a355a06fcc7ef2232736dceb012ae623335cd7ab (patch) | |
| tree | ff798546cd7f7e32f981b20ed7610a1e585ddd02 /Doc | |
| parent | 19e3e0026417caa92ffe21a67157363b45da9aa2 (diff) | |
| download | cpython-a355a06fcc7ef2232736dceb012ae623335cd7ab.zip cpython-a355a06fcc7ef2232736dceb012ae623335cd7ab.tar.gz cpython-a355a06fcc7ef2232736dceb012ae623335cd7ab.tar.bz2 | |
Fix typo in multiprocessing documentation (GH-20016)
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/library/multiprocessing.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index 50b9003..08258a6 100644 --- a/Doc/library/multiprocessing.rst +++ b/Doc/library/multiprocessing.rst @@ -2144,7 +2144,7 @@ with the :class:`Pool` class. or by calling :meth:`close` and :meth:`terminate` manually. Failure to do this can lead to the process hanging on finalization. - Note that is **not correct** to rely on the garbage colletor to destroy the pool + Note that it is **not correct** to rely on the garbage collector to destroy the pool as CPython does not assure that the finalizer of the pool will be called (see :meth:`object.__del__` for more information). |