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 Alexander.Belopolsky, Arfrever, asvetlov, brian.curtin, csernazs, cvrebert, dstanek, eric.araujo, eric.smith, giampaolo.rodola, holdenweb, larry, ncoghlan, r.david.murray, vstinner
Date 2012-04-01.14:40:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Which just goes to show that using Popen correctly is not obvious, I suppose.

Given that adding these errors *would* break backward compatibility, there would have to be a deprecation if it was done.

Personally I don't see the point in adding new class methods (complicating the interface) unless we are going to deprecate the current which case why not just deprecate the incorrect way of calling it?  (Note: I say incorrect because the 'call a different shell' variant *doesn't work* unless you write a custom shell that ignores '-c', and as Chris points out there's no functionality *gained* by the windows variation, and there is confusion introduced as to exactly what is going on).

So, if we aren't going to deprecate the "incorrect" calls, I vote for just closing this issue as "won't fix".

(I suppose that a third alternative exists: make the "incorrect" calls actually do something useful while preserving backward compatibility with the existing behavior.  That may be difficult, especially doing it in a way that logically consistent cross-platform.)
Date User Action Args
2012-04-01 14:40:49r.david.murraysetrecipients: + r.david.murray, holdenweb, csernazs, ncoghlan, vstinner, dstanek, larry, eric.smith, giampaolo.rodola, eric.araujo, Arfrever, brian.curtin, cvrebert, asvetlov, Alexander.Belopolsky
2012-04-01 14:40:49r.david.murraysetmessageid: <>
2012-04-01 14:40:49r.david.murraylinkissue7839 messages
2012-04-01 14:40:48r.david.murraycreate