On 14-11-2010 16:07, Dominic van Berkel wrote: > Hi all, > > It appears that I have managed to loop a ProcessProtocol subclass's > transport.write() right back into its outReceived. It's not directly > called, which leads me to believe that somehow stdin and stdout got tied > up. Anything thrown at transport.write() doesn't appear to reach the > actual process. I checked by running `cat > log` through it, the file > 'log' is created but remains empty. > > I am baffled, but will continue to poke at it. In the meantime, I'd > love to hear if anyone has a clue as to what I might have messed up. > > Thanks,
Forgot to mention that the ProcessProtocol instance does receive whatever the process sends my way. -- Dominic van Berkel "You don't have conversations with microprocessors. You tell them what to do, then helplessly watch the disaster when they take you literally." - David Brin, Startide Rising
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
