Terry J. Reedy added the comment: (Peter, the OP claims this issue is similar to a subprocess issue you fixed. I hope you can comment.)
Nearly identical versions of your example run from IDLE on both 2.7.3 and 3.3.0. Please rerun on 2.7.3 to make sure you have the problem with current Python. And if you do, try again when 2.7.4 comes out (date uncertain). I have no idea what STAF is, but we on this tracker are not responsible for 3rd party environments. It looks like STAF manipulates i/o streams# in a way that subprocess cannot handle*. The error has nothing to do with the particular command you tried to run. I suggest you present your problem to the STAF people. We can only handles identified problems within our code and we need a reproducible example that runs independent of such 3rd party environments. Without that, we will have to close this. # IDLE also manipulates the i/o streams and it has had i/o replacement stream bugs that we only fixed within the last 6 months. * For instance, I tried to run subprocess with stdout= <StringIO object>, to avoid writing to disk, but that failed, also within _get_handles(stdin, stdout, stderr), because StringIO objects do not have a fileno attribute. An error traceback is a graceful shutdown. A crash is an exit with no traceback and, on Windows, a popup or worse, a 'blue screen of death' and a reboot. (If you have never seen the latter, good for you and your system ;-). ---------- nosy: +astrand, terry.reedy stage: -> test needed type: crash -> behavior _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17350> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
