[Python-3000] failing tests

Guido van Rossum guido at python.org
Mon May 7 16:28:10 CEST 2007

Thanks for checking in xrange!!!!! Woot!

test_compiler and test_transformer are waiting for someone to clean up
the compiler package (I forget what it doesn't support, perhapes only
nonlocal needs to be added.)

Looks like you diagnosed the doctest failure correctly. This is
probably because, when print changed into print(), lines ending in
spaces are generated in some cases:

  # Py 2 code, writes "42\n"
  print 42,

  # Py3k automatically translated, writes "42 \n"
  print(42, end=" ")

I'm afraid we'll have to track down the places where this affects the
doctest and fix them. (Fixing the doctest is possible too, though less
elegant: just add <space> \n\ to the end of the line.)


On 5/7/07, Neal Norwitz <nnorwitz at gmail.com> wrote:
> There are 3* failing tests:
>     test_compiler test_doctest test_transformer
> * plus a few more when running on a 64-bit platform
> These failures occurred before and after xrange checkin.
> Do other people see these failures?  Any ideas when they started?
> The doctest failures are due to no space at the end of the line (print
> behavior change).  Not sure what to do about that now that we prevent
> blanks at the end of lines from being checked in. :-)
> n
> _______________________________________________
> Python-3000 mailing list
> Python-3000 at python.org
> http://mail.python.org/mailman/listinfo/python-3000
> Unsubscribe: http://mail.python.org/mailman/options/python-3000/guido%40python.org

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-3000 mailing list