Message317602
| Author | yselivanov |
|---|---|
| Recipients | asvetlov, serhiy.storchaka, yselivanov |
| Date | 2018-05-24.18:28:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1527186504.17.0.682650639539.issue33623@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Then we should find what callable is NULL and fix the place where it is called. _PyObject_FastCallDict() should never be called with NULL. My understanding is that the interpreter is being shutdown and half of the objects are freed. We're still holding a reference to *something* in Python space and try calling it. The obvious fix for that is simply avoid capturing tracebacks if a Future object is created during finalization of the interpreter (it's pointless to capture it anyways at that point). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-05-24 18:28:24 | yselivanov | set | recipients: + yselivanov, asvetlov, serhiy.storchaka |
| 2018-05-24 18:28:24 | yselivanov | set | messageid: <1527186504.17.0.682650639539.issue33623@psf.upfronthosting.co.za> |
| 2018-05-24 18:28:24 | yselivanov | link | issue33623 messages |
| 2018-05-24 18:28:24 | yselivanov | create | |