-On [20080108 12:09], Nick Coghlan ([EMAIL PROTECTED]) wrote:
>Redirecting stdout also fails for both the trunk and the py3k branch for
>me on Ubuntu. If I redirected stderr as well then the tests worked again.
>
>Given that a pipe/file and the console very likely *do* have different
>encodings,
Guido van Rossum wrote:
> No answers yet, but a clue, and anyone on OSX should now be able to
> reproduce this (with 2.5, 2.6 or 3.0) as follows:
>
> ./python ./Lib/test/test_sys.py | cat
>
> That is, the problem happens when stdout is redirected to a pipe (or a file).
Redirecting stdout also
On Dec 21, 2007 12:05 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > When I build from scratch and run most tests (regrtest.py -uall) I get
> > some strange failures with test_sys.py:
> >
> > test test_sys failed -- Traceback (most recent call last):
> > File "/usr/loca
Guido van Rossum wrote:
> When I build from scratch and run most tests (regrtest.py -uall) I get
> some strange failures with test_sys.py:
>
> test test_sys failed -- Traceback (most recent call last):
> File "/usr/local/google/home/guido/python/py3kd/Lib/test/test_sys.py",
> line 302, in test_4
I am unable to reproduce this in windows with:
Python 3.0a2 (py3k:59584M, Dec 20 2007, 16:24:12) [MSC v.1500 32 bit
(Intel)] on win32
Running the test via rt and in isolation does not appear to fail. In
isolation produces 16 OKs.
Joe
On Dec 20, 2007 3:58 PM, Guido van Rossum <[EMAIL PROTECTED]
