Message232140
| Author | vstinner |
|---|---|
| Recipients | arigo, neologix, nikratio, serhiy.storchaka, tim.peters, vstinner |
| Date | 2014-12-04.15:41:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAMpsgwbhaVYz0TQ78czNBMUMpSigQU2wrXcxouQkgxe-g3Gagw@mail.gmail.com> |
| In-reply-to | <1417701973.66.0.486200538948.issue17852@psf.upfronthosting.co.za> |
| Content | |
|---|---|
By the way, I fixed various issues to ensure that ResourceWarning are displayed at Python exit. There are still corner cases when the warnings are not emited. For example, when a daemon thread is used. Or when the warning comes very late during Python finalization. Recent example of tricky issue related to this warning: #22898. IMO it's a bug, it must be fixed and it should be possible to emit the warning. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-12-04 15:41:13 | vstinner | set | recipients: + vstinner, tim.peters, arigo, nikratio, neologix, serhiy.storchaka |
| 2014-12-04 15:41:13 | vstinner | link | issue17852 messages |
| 2014-12-04 15:41:13 | vstinner | create | |