[issue23342] run() - unified high-level interface for subprocess

[Jeff Hammel]

Jeff Hammel added the comment:

A few observations in passing.  I beg your pardon for not commenting after a more in depth study of the issue, but as someone that's written and managed several subprocess module front-ends, my general observations seem applicable.

subprocess needs easier and more robust ways of managing input and output streams

subprocess should have easier ways of managing input: file streams are fine, but plain strings would also be nice

for string commands, shell should always be true. for list/Tupperware commands, shell should be false. in fact you'll get an error if you don't ensure this. instead, just have what is passed key execution (for windows, I have no idea. I'm lucky enough not to write windows software these days)

subprocess should always terminate processes on program exit robustly (unless asked not too). I always have a hard time figuring out how to get processes to terminate, and how to have them not to.  I realize POSIX is black magic, to some degree.

I'm attaching a far from perfect front end that I currently use for reference

----------
nosy: +Jeff.Hammel
Added file: http://bugs.python.org/file38075/process.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23342>
_______________________________________