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 pitrou
Recipients Windson Yang, davin, docs@python, mattip, pitrou, tzickel, zach.ware
Date 2018-07-23.16:38:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What other object in the standard lib, leaks resources when deleted in CPython ?

Threads come to mind, for example:

>>> import time, threading, weakref
>>> t = threading.Thread(target=time.sleep, args=(100000,))
>>> t.start()
>>> wr = weakref.ref(t)
>>> del t
>>> wr()
<Thread(Thread-1, started 139937234327296)>

Note I'm not against fixing this issue, just saying it's not that surprising for Pool to keep lingering around when you lost any user-visible reference to it.
Date User Action Args
2018-07-23 16:38:06pitrousetrecipients: + pitrou, docs@python, zach.ware, mattip, davin, tzickel, Windson Yang
2018-07-23 16:38:06pitrousetmessageid: <>
2018-07-23 16:38:06pitroulinkissue34172 messages
2018-07-23 16:38:05pitroucreate