➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tzickel
Recipients tzickel
Date 2018-07-20.16:45:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
In-reply-to
Content 
In multiprocessing.Pool documentation it's written "When the pool object is garbage collected terminate() will be called immediately.":

https://docs.python.org/3.7/library/multiprocessing.html#multiprocessing.pool.Pool.terminate

A. This does not happen, creating a Pool, deleting it and collecting the garbage, does not call terminate.

B. The documentation for Pool itself does not specify it has a context manager (but the examples show it).

C. This bug is both in Python 3 & 2.
History
Date User Action Args
2018-07-20 16:45:29tzickelsetrecipients: + tzickel
2018-07-20 16:45:29tzickelsetmessageid: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
2018-07-20 16:45:29tzickellinkissue34172 messages
2018-07-20 16:45:29tzickelcreate