python regression tests - a monster hammer to keep wine "in check" :)
Luke Kenneth Casson Leighton
lkcl at lkcl.net
Sat Jan 17 04:42:46 CST 2009
i've started running the python regression tests under wine (using the
build of python i've only just created) and have started filling in
bugreports for the tests that fail, but some things occurred to me:
1) why am i the only person filling out the bugreports? :)
2) surely these regression tests would work equally as well under the
python2.5.2.exe that you can get as part of the pre-prepared python
win32 install that comes from python.org and activestate.com, you
don't _need_ my wine-built version of python.exe
3) why am i considering rewriting the tests as c-code when they can
just as well be left as python code?
one of the bugs that's _really_ really important is: crlf conversion.
the code in wine's msvcrt is completely borked. i demonstrated this
by switching over to "native" msvcrt.dll, and nearly _all_ of the 12
tests that failed, all but the test_os.py ones miraculously succeeded.
the majority of tests fail due to file corruption over writing \n and
getting back \r\n, which is clearly bogus. _yes_ i'm aware of the
difference between O_BINARY and O_TEXT, and it would seem that there's
either a default setting which is wrong, or there's some runtime
detection going on, or... just... _something_ :)
but the behaviour of msvcrt wrt crlf is _definitely_ not right, as it
stands, and as a result it completely screws any possibility for
running python.exe under wine. completely. you can't have files that
you write to, that are different from when they are read back.
More information about the wine-devel