On 10/8/05, Neal Norwitz <[EMAIL PROTECTED]> wrote: > On 10/8/05, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > Hye-Shik Chang wrote: > > > On 10/8/05, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > > > > >>Anyone else seeing any problems with test_cmd_line? I've got a few > > >>failures in > > >>test_cmd_line on Kubuntu 5.10 with GCC 4.0 relating to a missing "\n" > > >>line ending. > > > > If I explicitly write Ctrl-D to the subprocess's stdin for the tests which > > open the interpreter, then the tests pass. So it looks like some sort of > > buffering problem with standard out not getting flushed before the test > > tries > > to read the data. > > Sorry, that's a new test I added recently. It works for me on gentoo. > The test is very simple and shouldn't be hard to fix. Can you fix > it? I assume Guido (or someone) added you as a developer. If not, if > you can give me enough info, I can try to fix it.
I guess Neil's test was expecting at least one line of output from python at all times, but on most systems it is completely silent when the input is empty. I fixed the test (also in 2.4) to allow empty input as well as input ending in \n. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
