[Python-Dev] New regrtest.py gimmick

Tim Peters tim.one@home.com
Sat, 11 Aug 2001 21:24:15 -0400

Since checkin email isn't working, I'm sending this to Python-Dev.

More than once I've been burned by tests getting skipped on Windows when
they shouldn't have been.  Indeed, for at least one release we didn't ship
the XML libraries on Windows because I had no idea the associated tests
weren't *supposed* to get skipped.

regrtest.py now prints this for me (note the last line):

138 tests OK.
25 tests skipped: test_al test_cd test_cl test_commands test_crypt
    test_dbm test_dl test_fcntl test_fork1 test_gdbm test_gl test_grp
    test_imgfile test_largefile test_linuxaudiodev test_mhlib test_nis
    test_openpty test_poll test_pty test_pwd test_signal
    test_socketserver test_sunaudiodev test_timing
Those skips are all expected on win32.

For you it will print something like:

MMM tests OK.
NN tests skipped: XXX YYY ...
Ask someone to teach regrtest.py about which tests are
expected to get skipped on [sys.platform].

You do that by changing the new _ExpectedSkips.__init__ near the bottom of

If sys.platform isn't enough to determine the set of skipped tests, then
sys.platform isn't particularly useful <0.9 wink>.