[issue11459] Python select.select does not correctly report read readyness

2011-03-09 Thread Novimir Pablant
New submission from Novimir Pablant : I am trying to get the output from an external program into python using `subprocess.Popen` and `select.select`. For some reason though select.select is at times telling me that stdout is not ready to read, even when it is (reading from it works

[issue11459] Python select.select does not correctly report read readyness

2011-03-09 Thread Novimir Pablant
Novimir Pablant added the comment: I forgot to mention, I am running on OS X 10.6.6. -- ___ Python tracker <http://bugs.python.org/issue11459> ___ ___ Python-bug

[issue11459] Python select.select does not correctly report read readyness

2011-03-10 Thread Novimir Pablant
Novimir Pablant added the comment: Applying the patch appears to fix this problem. Thanks! I am definitely confused about why the buffer was changed to line buffered in the first place, especially since the default is bufsize=0 and the comment ("# Nearly unbuffered (XXX for now)"

[issue11459] Python select.select does not correctly report read readyness

2011-03-16 Thread Novimir Pablant
Novimir Pablant added the comment: I agree with Gregory that fixing this in 3.1 and 3.2 is the way to go. Otherwise I would suggest changing the documentation to match the behavior. -- ___ Python tracker <http://bugs.python.org/issue11