Message235663
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 |
|
Date |
User |
Action |
Args |
2015-02-10 03:49:23 | Jeff.Hammel | set | recipients:
+ Jeff.Hammel, barry, gregory.p.smith, r.david.murray, cvrebert, ethan.furman, takluyver, martin.panter |
2015-02-10 03:49:23 | Jeff.Hammel | set | messageid: <1423540163.72.0.841842841705.issue23342@psf.upfronthosting.co.za> |
2015-02-10 03:49:23 | Jeff.Hammel | link | issue23342 messages |
2015-02-10 03:49:23 | Jeff.Hammel | create | |
|