[docs] [issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted

[STINNER Victor]

STINNER Victor <vstinner at redhat.com> added the comment:

multiprocessing.Pool destructor now emits a ResourceWarning if it is still running: if .close() nor .terminate() have been called, see bpo- 35424.

It is a first alarm that the problematic example is wrong.

Should reconsider to fix this bug in the master branch? If yes, we should carefully document this backward incompatible change.

----------

______________________________________________
Python tracker <cpython at roundup.psfhosted.org>
<https://bugs.python.org/issue34172>
______________________________________________