[issue16635] Interpreter not closing stdout/stderr on exit
Filip Zyzniewski
report at bugs.python.org
Fri Dec 7 15:08:03 CET 2012
Filip Zyzniewski added the comment:
If stdout was closed before closing stderr, then stdout problems could be reported, and that is what I would expect when using Python this way.
os.fsync(1) helps, but only if preceeded by sys.stdout.flush() and it seems a bit cumbersome.
Is there any downside to doing close(1) explicitely?
cat, grep, dd and echo close their stdout, why couldn't Python do this?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16635>
_______________________________________
More information about the Python-bugs-list
mailing list