[issue1366] popen spawned process may not write to stdout under windows

2008-12-05 Thread Georg Brandl
Changes by Georg Brandl <[EMAIL PROTECTED]>: -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list m

[issue1366] popen spawned process may not write to stdout under windows

2008-07-16 Thread Georg Brandl
Georg Brandl <[EMAIL PROTECTED]> added the comment: Did you want to close this, Sean? -- nosy: +georg.brandl ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1366] popen spawned process may not write to stdout under windows

2008-03-17 Thread Sean Reifschneider
Sean Reifschneider <[EMAIL PROTECTED]> added the comment: We've discussed this at the PyCon sprints, and here's the concensus: os.popen inherits the parents stderr, and on Windows there is not an existing valid stderr by default. So the parent should, to be compatible with the Windows environme

[issue1366] popen spawned process may not write to stdout under windows

2007-11-08 Thread Patrick Mézard
Patrick Mézard added the comment: pythonmeister: I never expected stderr to be redirected, just *all stdout* to be captured. But... gagenellina: you are completely right about the failure. Still, this issue happened with a real world application written in C, and redirecting manually stderr to :

[issue1366] popen spawned process may not write to stdout under windows

2007-11-08 Thread Stefan Sonnenberg-Carstens
Stefan Sonnenberg-Carstens added the comment: the popen call does not redirect stderr. If you do something like 2>null (windows) or 2>/dev/null (*nix) it will _never_ get printed. If you want to have stderr & stdout getting in via popen and thus stdout, under *nix and windows you would do that:

[issue1366] popen spawned process may not write to stdout under windows

2007-11-07 Thread Gabriel Genellina
Gabriel Genellina added the comment: (I think the title you meant was "popen spawned process may not write to stderr under windows") The child is dying with IOError: [Errno 22] Invalid argument at the sys.stderr.flush() call. Neither the docs for os.popen nor the Linux man page for popen(3)

[issue1366] popen spawned process may not write to stdout under windows

2007-10-31 Thread Patrick Mézard
New submission from Patrick Mézard: Let child.py be: """ import sys sys.stdout.write('1:stdout\n') sys.stdout.flush() sys.stderr.write('2:stderr\n') sys.stderr.flush() sys.stdout.write('3:stdout\n') sys.stdout.flush() """ and parent.py: """ import os cmd = 'python child.py' for l in os.popen(c