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 vstinner
Recipients Windson Yang, benjamin.peterson, davin, docs@python, mattip, ned.deily, pablogsal, pitrou, tzickel, vstinner, zach.ware
Date 2018-12-21.15:38:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.
Date User Action Args
2018-12-21 15:38:05vstinnersetrecipients: + vstinner, pitrou, benjamin.peterson, ned.deily, docs@python, zach.ware, mattip, davin, tzickel, pablogsal, Windson Yang
2018-12-21 15:38:03vstinnersetmessageid: <>
2018-12-21 15:38:03vstinnerlinkissue34172 messages
2018-12-21 15:38:03vstinnercreate