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 yselivanov
Recipients asvetlov, serhiy.storchaka, yselivanov
Date 2018-05-24.18:28:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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).
Date User Action Args
2018-05-24 18:28:24yselivanovsetrecipients: + yselivanov, asvetlov, serhiy.storchaka
2018-05-24 18:28:24yselivanovsetmessageid: <>
2018-05-24 18:28:24yselivanovlinkissue33623 messages
2018-05-24 18:28:24yselivanovcreate