[Neal Norwitz]
> ...
> I couldn't let Trent have all the fun.
>
> http://docs.python.org/dev/
>
> And hopefully of interest to many here:
>
> http://docs.python.org/dev/results/
Wow! You get no test failures! I guess nobody tests on Windows
anymore. I've been getting test failures for months, and just
_assumed_ this was known damage everywhere so was waiting for someone
else to fix it ;-) (A parenthentical question: is there a reason you
don't pass -uall to regrtest.py?)
On WinXP Pro SP2 today, passing -uall, and after fixing all the MS
compiler warnings that have crept in:
251 tests OK.
12 tests failed:
test_builtin test_coding test_compiler test_pep263
test_univnewlines test_urllib test_urllib2 test_urllibnet
test_userlist test_wave test_whichdb test_zipfile
39 tests skipped:
test__locale test_aepack test_al test_applesingle test_bsddb185
test_cd test_cl test_commands test_crypt test_curses test_dbm
test_dl test_fcntl test_fork1 test_gdbm test_gl test_grp
test_hashlib_speed test_imgfile test_ioctl test_linuxaudiodev
test_macfs test_macostools test_mhlib test_nis test_openpty
test_ossaudiodev test_plistlib test_poll test_posix test_pty
test_pwd test_resource test_scriptpackages test_signal
test_sunaudiodev test_threadsignals test_timing test_xml_etree_c
1 skip unexpected on win32:
test_xml_etree_c
Where to begin? Let's start with the first:
C:\Code\python\PCbuild>rt -q test_builtin
C:\Code\python\PCbuild>python -E -tt ../lib/test/regrtest.py test_builtin
test_builtin
test test_builtin failed -- errors occurred; run in verbose mode for details
1 test failed:
test_builtin
OK, try again:
C:\Code\python\PCbuild>rt -q -v test_builtin
C:\Code\python\PCbuild>python -E -tt ../lib/test/regrtest.py -v test_builtin
test_builtin
test_abs (test.test_builtin.BuiltinTest) ... ok
...
======================================================================
ERROR: test_compile (test.test_builtin.BuiltinTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Code\python\lib\test\test_builtin.py", line 237, in test_compile
compile(bom + 'print 1\n', '', 'exec')
File "<string>", line 1
∩�[┐print 1
^
SyntaxError: invalid syntax
======================================================================
ERROR: test_eval (test.test_builtin.BuiltinTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Code\python\lib\test\test_builtin.py", line 306, in test_eval
self.assertEqual(eval(bom + 'a', globals, locals), 1)
File "<string>", line 1
∩�[┐a
^
SyntaxError: invalid syntax
I have no idea what those are trying to test, and remember guessing
the first time I saw this that it was fallout from the AST-branch
merge. Apparently it wasn't :-(. Anyone have a clue on this one?
The code up to the first failure is short:
bom = '\xef\xbb\xbf'
compile(bom + 'print 1\n', '', 'exec')
Curiously, that sequence doesn't blow up under the released Windows
Python 2.4.2, so somebody broke something here since then ...
_______________________________________________
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
