Re: BUG pythonw vs subprocess

Robin Becker <[EMAIL PROTECTED]> wrote: >John J. Lee wrote: >> Paul Rubin writes: >> >>>I thought pythonw didn't provide a console and so it could be that >>>stdin and stdout aren't connected to anything. Popen therefore doesn't >>>make sense. You have to use sockets o

Re: BUG pythonw vs subprocess

Paul Rubin wrote: > I thought pythonw didn't provide a console and so it could be that > stdin and stdout aren't connected to anything. Popen therefore doesn't > make sense. You have to use sockets or something. Well my example is explicitly using PIPE for stderr & stdin, but I don't know how t

Re: BUG pythonw vs subprocess

John J. Lee wrote: > Paul Rubin writes: > > >>I thought pythonw didn't provide a console and so it could be that >>stdin and stdout aren't connected to anything. Popen therefore doesn't >>make sense. You have to use sockets or something. > > > Yeah... I don't know a

Re: BUG pythonw vs subprocess

Paul Rubin writes: > I thought pythonw didn't provide a console and so it could be that > stdin and stdout aren't connected to anything. Popen therefore doesn't > make sense. You have to use sockets or something. Yeah... I don't know about module subprocess, but I rec

Re: BUG pythonw vs subprocess

Paul Rubin wrote: > >I thought pythonw didn't provide a console and so it could be that >stdin and stdout aren't connected to anything. Popen therefore doesn't >make sense. You have to use sockets or something. Exactly right. The error message is quite accurate: non-c

Re: BUG pythonw vs subprocess

I thought pythonw didn't provide a console and so it could be that stdin and stdout aren't connected to anything. Popen therefore doesn't make sense. You have to use sockets or something. -- http://mail.python.org/mailman/listinfo/python-list