Guido van Rossum added the comment:
This is how C stdio works in the subprocess. Python's subprocess.py has
nothing to do with it and can't do anything about it.
--
nosy: +gvanrossum
resolution: -> invalid
status: open -> closed
__
Tracker <[EMAIL PROTE
Peter Ã…strand added the comment:
Most probably, this is not a problem with the Python side or the pipes,
but the libc streams in the application. stderr is normally unbuffered,
while stdout is buffered. You can see this by running the app with grep:
$ ./a.out | grep STDOUT
STDERR sleeping 0
STD
New submission from Jason Kim:
Hi.
I am currently using subprocess.py (2.4.4 and above) to try to have a
portable way of running a sub task in linux and windows.
I ran into a strange problem - a program runs and is "timed out"
but the the subprocess's stdout and stderr are not fully "grabbed"
