> My guess is that since `d` is at the global scope, it doesn't get garbage
> collected until some unfortunately late phase in the interpreter tear-down
> where maybe stderr isn't even available any more.
Here be dragons.
>
> I'd definitely ignore this case for now and fix the others, which are
> On May 30, 2018, at 10:04 PM, Jason Litzinger wrote:
>
> Any thoughts on why no traceback is printed for case 1? Is it even
> worth worrying about?
My guess is that since `d` is at the global scope, it doesn't get garbage
collected until some unfortunately late phase in the interpreter tea
I've been looking at cleaning up cases where a traceback isn't printed
for deferreds with an unhandled error, and there is one strange case I'm
hoping someone might have thoughts about*. For reference, some of this is part
of 7927 and related tickets.
Consider:
from __future__ import print_functi
