Re: [Twisted-Python] ProcessProtocol stdin/stdout loop

2010-11-14 Thread Dominic van Berkel
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

[Twisted-Python] ProcessProtocol stdin/stdout loop

2010-11-14 Thread Dominic van Berkel
each 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, -- Dominic van Ber

Re: [Twisted-Python] Knowing whether spawnProcess did anything useful

2010-07-14 Thread Dominic van Berkel
eactor would probably be a fine idea, yeah. The code I've got on file does all the subclassing and even starts the reactor, I just blindly forgot to start the reactor on the REPL. That's what I get for copying the base of my code from an example. Thanks! -- Dominic van Berkel "Y

[Twisted-Python] Knowing whether spawnProcess did anything useful

2010-07-13 Thread Dominic van Berkel
believe that there's no way to do this, though. Thanks. [1] http://twistedmatrix.com/documents/current/api/twisted.internet.interfaces.IProcessTransport.html#pid -- Dominic van Berkel "You don't have conversations with microprocessors. You tell them what to do, then helplessly watch the di