Phil Vandry TZoNE.ORG> writes:
> proc.stdin, proc.stdout, and proc.stderr aren't meant to be a reference
> to the file that got connected to the subprocess' stdin/stdout/stderr.
> They are meant to be a reference to the OTHER END of the pipe that got
> connected.
Of course, and I've been usi
On Sun, 8 Jan 2012 02:06:33 + (UTC)
Vinay Sajip wrote:
> Mike Meyer mired.org> writes:
>
> > Since the only reason they exist is so you can access your end of a
> > pipe, setting them to anything would seem to be a bug. I'd argue that
> > their existence is more a pola violation than them h
On 2012-01-08 10:48 , Vinay Sajip wrote:
Terry Reedy udel.edu> writes:
The behavior matches the doc: Popen.stdin
If the stdin argument was PIPE, this attribute is a file object that
provides input to the child process. Otherwise, it is None.
Right, but it's not very helpful, nor especially i
That's documented behaviour nonetheless. I would agree that the behaviour is a
stupid one (not knowing the reason for it); even so it cannot be changed in a
backwards compatible way.
Am 07.01.2012 um 22:25 schrieb Vinay Sajip :
> The subprocess.Popen constructor takes stdin, stdout and stderr k
Mike Meyer mired.org> writes:
> Since the only reason they exist is so you can access your end of a
> pipe, setting them to anything would seem to be a bug. I'd argue that
> their existence is more a pola violation than them having the value
> None. But None is easier than a call to hasattr.
I d
Terry Reedy udel.edu> writes:
> The behavior matches the doc: Popen.stdin
> If the stdin argument was PIPE, this attribute is a file object that
> provides input to the child process. Otherwise, it is None.
Right, but it's not very helpful, nor especially intuitive. Why does it have to
be None
On Sat, 7 Jan 2012 21:25:37 + (UTC)
Vinay Sajip wrote:
> The subprocess.Popen constructor takes stdin, stdout and stderr keyword
> arguments which are supposed to represent the file handles of the child
> process.
> The object also has stdin, stdout and stderr attributes, which one would
>
On 1/7/2012 4:25 PM, Vinay Sajip wrote:
The subprocess.Popen constructor takes stdin, stdout and stderr keyword
arguments which are supposed to represent the file handles of the child process.
The object also has stdin, stdout and stderr attributes, which one would naively
expect to correspond to
The subprocess.Popen constructor takes stdin, stdout and stderr keyword
arguments which are supposed to represent the file handles of the child process.
The object also has stdin, stdout and stderr attributes, which one would naively
expect to correspond to the passed in values, except where you pa
