Message300455
| Author | pitrou |
|---|---|
| Recipients | JohanAR, davin, itamarst, ncoghlan, pitrou, python-dev, rhettinger, sbt, tim.peters, yselivanov, zzzeek |
| Date | 2017-08-17.20:01:27 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1503000087.84.0.923037727756.issue14976@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Using any kind of potentially-blocking synchronization primitive from __del__ or weakref callback is indeed a bug waiting for happen. I agree non-trivial cases can be hard to debug, especially when people don't expect that kind of cause. It would be ok to submit a patch solving this issue using C code IMHO. Note the maxsize argument complicates things even though most uses of Queue don't use maxsize. Of course, the general issue isn't only about Queue: other synchronization primitives are widely used. See https://github.com/tornadoweb/tornado/pull/1876 for an example. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-08-17 20:01:27 | pitrou | set | recipients: + pitrou, tim.peters, rhettinger, ncoghlan, zzzeek, python-dev, sbt, JohanAR, yselivanov, itamarst, davin |
| 2017-08-17 20:01:27 | pitrou | set | messageid: <1503000087.84.0.923037727756.issue14976@psf.upfronthosting.co.za> |
| 2017-08-17 20:01:27 | pitrou | link | issue14976 messages |
| 2017-08-17 20:01:27 | pitrou | create | |