[Python-3000] status (preparing for first alpha)

[Thomas Heller]

Neal Norwitz schrieb:
> Py3k is progressing nicely.  We are planning the first alpha sometime
> this week.  The tests are mostly passing.  With all the churn over the
> last week, I'm sure it's about to change.  :-)  AFAIK, nearly all the
> tests pass on Linux and Mac OS X.  There was a report that Windows/VC8
> was able to build python but it crashed in test_builtin.  Can anyone
> confirm this?
> 
> Here are the tasks that we need help with before the alpha is released:
>  * Verify Windows build works with VC7 (currently the default compiler for 2.5)

The build works for me, now that I've fixed PCBuild\build_ssl.py for Python3.

>  * Verify Windows build passes all tests
Hehe.

For me Python3 still cannot 'import time', because of umlauts in the _tzname
libc variable:

  c:\svn\py3k\PCbuild>python_d
  Python 3.0x (py3k:57555, Aug 27 2007, 10:00:25) [MSC v.1310 32 bit (Intel)] on win32
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import time
  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
  UnicodeDecodeError: 'utf8' codec can't decode bytes in position 9-11: invalid data
  [36397 refs]
  >>>

Setting the environment variable TZ to 'GMT' for example is a workaround for this problem.


Running the PCBuild\rt.bat script fails when it compares the expected output
with the actual output.  Some inspection shows that the comparison fails because
there are '\n' linefeeds in the expected and '\n\r' linefeeds in the actual output:

  c:\svn\py3k\PCbuild>python_d  -E -tt ../lib/test/regrtest.py
  test_grammar
  test test_grammar produced unexpected output:
  **********************************************************************
  *** mismatch between line 1 of expected output and line 1 of actual output:
  - test_grammar
  + test_grammar
  ?             +
  (['test_grammar\n'], ['test_grammar\r\n'])
  ... and so on ...

(The last line is printed by some code I added to Lib\regrtest.py.)

It seems that this behaviour was introduced by r57186:

  New I/O code from Tony Lownds implement newline feature correctly,
  and implements .newlines attribute in a 2.x-compatible fashion.

Temporarily reverting this change from Lib\io.py I can run the tests
without all this comparison failures.  What I see is:

...
test test_builtin failed -- Traceback (most recent call last):
  File "c:\svn\py3k\lib\test\test_builtin.py", line 1473, in test_round
    self.assertEqual(round(1e20), 1e20)
AssertionError: 0 != 1e+020
...
(a lot of failures in test_doctest.  Could this also be a line ending problem?)

Unicode errors in various tests:
  test_glob
  test test_glob failed -- Traceback (most recent call last):
    File "c:\svn\py3k\lib\test\test_glob.py", line 87, in test_glob_directory_names
      eq(self.glob('*', '*a'), [])
    File "c:\svn\py3k\lib\test\test_glob.py", line 41, in glob
      res = glob.glob(p)
    File "c:\svn\py3k\lib\glob.py", line 16, in glob
      return list(iglob(pathname))
    File "c:\svn\py3k\lib\glob.py", line 42, in iglob
      for name in glob_in_dir(dirname, basename):
    File "c:\svn\py3k\lib\glob.py", line 56, in glob1
      names = os.listdir(dirname)
  UnicodeDecodeError: 'utf8' codec can't decode bytes in position 27-31: unexpected end of data

I'll stop the report here.  A py3k buildbot on Windows would allow everyone to look at the test outcome.

Thomas