Message322231
| 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 | <1532363886.07.0.56676864532.issue34172@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-23 16:38:06 | pitrou | set | recipients: + pitrou, docs@python, zach.ware, mattip, davin, tzickel, Windson Yang |
| 2018-07-23 16:38:06 | pitrou | set | messageid: <1532363886.07.0.56676864532.issue34172@psf.upfronthosting.co.za> |
| 2018-07-23 16:38:06 | pitrou | link | issue34172 messages |
| 2018-07-23 16:38:05 | pitrou | create | |