This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients amaury.forgeotdarc, georg.brandl, mez, terry.reedy, tim.golden
Date 2008-12-05.22:14:12
SpamBayes Score 0.00024310757
Marked as misclassified No
Message-id <1228515254.35.0.788908852283.issue4488@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, the new docs are much better.  Methods are nicely identified in
2.6/3.0 docs that I checked.  There is one category that is not:
constants.  For instance, the following is from the subprocess doc.

"stdin, stdout and stderr specify the executed programs’ standard input,
standard output and standard error file handles, respectively. Valid
values are PIPE, an existing file descriptor (a positive integer), an
existing file object, and None. PIPE indicates that a new pipe to the
child should be created. With None, no redirection will occur; the
child’s file handles will be inherited from the parent. Additionally,
stderr can be STDOUT, which indicates that the stderr data from the
applications should be captured into the same file handle as for stdout."

As I discovered, neither 'PIPE' nor PIPE is valid, subprocess.PIPE is
what is required.  (Ditto for subprocess.STDOUT I presume.) Can such
names of constants be fully qualified just as method names are now?
History
Date User Action Args
2008-12-05 22:14:14terry.reedysetrecipients: + terry.reedy, georg.brandl, amaury.forgeotdarc, tim.golden, mez
2008-12-05 22:14:14terry.reedysetmessageid: <1228515254.35.0.788908852283.issue4488@psf.upfronthosting.co.za>
2008-12-05 22:14:13terry.reedylinkissue4488 messages
2008-12-05 22:14:12terry.reedycreate