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 takluyver
Recipients Jeff.Hammel, barry, cvrebert, ethan.furman, gregory.p.smith, martin.panter, r.david.murray, takluyver
Date 2015-02-11.04:10:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Jeff: This makes it somewhat easier to handle input and output as strings instead of streams. Most of the functionality was already there, but this makes it more broadly useful. It doesn't especially address your other points, but I'm not aiming to completely overhaul subprocess.

> for string commands, shell should always be true. for list/Tupperware commands, shell should be false

I wondered why this is not the case before, but on Windows a subprocess is actually launched by a string, not a list. And on POSIX, a string without shell=True is interpreted like a one-element list, so you can do e.g. Popen('ls') instead of Popen(['ls']). Changing that would probably break backwards compatibility in unexpected ways.
Date User Action Args
2015-02-11 04:10:29takluyversetrecipients: + takluyver, barry, gregory.p.smith, r.david.murray, cvrebert, ethan.furman, martin.panter, Jeff.Hammel
2015-02-11 04:10:29takluyversetmessageid: <>
2015-02-11 04:10:29takluyverlinkissue23342 messages
2015-02-11 04:10:29takluyvercreate