Re: [Twisted-Python] Re-entrancy policy for the reactor

On Sun, 2011-07-24 at 22:51 -0400, Itamar Turner-Trauring wrote:

This can lead to re-entrancy bugs. I am tempted to suggest a policy of No Reactor Reentrancy, but that is currently violated by one of the TCP half-close code paths, and producers if I'm not mistaken.

Instead of "No Reactor Re-entrancy", I meant "No Protocol Re-entrancy", i.e. the reactor only ever calls into a protocol once in a given call stack.