[ python-Bugs-918710 ] popen2 returns (out, in) not (in, out)

[SourceForge.net]

Bugs item #918710, was opened at 2004-03-18 12:44
Message generated for change (Comment added) made by insomnike
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=918710&group_id=5470

Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Yotam Medini (yotam)
Assigned to: Nobody/Anonymous (nobody)
Summary: popen2 returns (out, in) not (in, out)

Initial Comment:
http://python.org/doc/current/lib/os-newstreams.html#l2h-1379
says:

popen2(  	cmd[, mode[, bufsize]])
    Executes cmd as a sub-process.
    Returns the file objects (child_stdin, child_stdout). 

But for me it actually returns (child-output, child-input).
Or... is it a semantci issue?  that is 
  child_stdin - is "the input _from_ child?"
Anyway - it is confusing.


----------------------------------------------------------------------

Comment By: Aaron Brady (insomnike)
Date: 2004-06-05 16:44

Message:
Logged In: YES 
user_id=1057404

The above is not-a-bug, but this documentation patch below
might serve to remove any confusion.

###
--- libos.tex-  Sat Jun  5 17:28:52 2004
+++ libos.tex   Sat Jun  5 17:32:40 2004
@@ -384,6 +384,10 @@
 \versionadded{2.0}
 \end{funcdesc}

+It should be noted that \code{\var{child_stdin},
\var{child_stdout}, and
+\var{child_stderr}} are named from the child process' point
of view, i.e. the
+stdin of the child.
+
 This functionality is also available in the
\refmodule{popen2} module
 using functions of the same names, but the return values of
those
 functions have a different order.
###

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=918710&group_id=5470