Hey, sorry, just saw this question right now. Actually, I don't know. I assume this is not standard, because many excepthook handlers would probably print some

Hey, sorry, just saw this question right now. Actually, I don't know. I assume this is not standard, because many excepthook handlers would probably print some variant of the stack trace on stdout or stderr, and then you would end up having printed the stack trace multiple times. Or maybe it depends. If your excepthook instead prints it somewhere else (e.g. some log file), it makes sense to also call the default handler afterwards. But no, this is not about the closure.