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 r.david.murray
Recipients CristianCantoro, r.david.murray
Date 2014-08-27.13:56:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409147773.21.0.546701624463.issue22277@psf.upfronthosting.co.za>
In-reply-to
Content
I think it is up to you motivate the reason why the new stdin and stderr parameters should have *different* semantics from the same parameters used with subprocess.  Consistency is good, unless there is a specific reason to break consistency.  That is, if the semantics are the same, a programmer can see stdin/stderr and know they work exactly like the equivalent subprocess args, instead of assuming they do and then getting bitten by the difference.

Unless there is some reason I'm not seeing why the difference in semantics is needed.
History
Date User Action Args
2014-08-27 13:56:13r.david.murraysetrecipients: + r.david.murray, CristianCantoro
2014-08-27 13:56:13r.david.murraysetmessageid: <1409147773.21.0.546701624463.issue22277@psf.upfronthosting.co.za>
2014-08-27 13:56:13r.david.murraylinkissue22277 messages
2014-08-27 13:56:13r.david.murraycreate