Paul Rubin <> writes:
> Nikolaus Rath <> writes:
>> Still no context before the ominous close() call. I'm very confused.
> close() could be getting called from a destructor as the top level
> function of a thread exits, or something like that.

Shouldn't the destructor have its own stack frame then, i.e. shouldn't
the first frame be in a __del__ function?


GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Reply via email to