[Python-Dev] Re: Testing the 2.2.2 email pkg

[Tim Peters]

This gets too confusing too fast.  test_email fails under 2.3 CVS for me
this morning too, no matter how I run it -- via regrtest, by itself, doesn't
matter.

STRAIGHT REGREST
>python ../lib/test/regrtest.py test_email
test_email
test test_email failed -- errors occurred; run in verbose mode for details
1 test failed:
    test_email


DITTO BUT VERBOSE
>python ../lib/test/regrtest.py -v test_email
... lots of error output ...
Ran 164 tests in 1.150s
FAILED (failures=33, errors=4)
test test_email failed -- errors occurred; run in verbose mode for details
1 test failed:
    test_email

BY ITSELF
>python ../lib/test/test_email.py
... lots of error output ...
Ran 164 tests in 1.150s

FAILED (failures=33, errors=4)
Traceback (most recent call last):
  File "../lib/test/test_email.py", line 13, in ?
    test_main()
  File "../lib/test/test_email.py", line 10, in test_main
    run_suite(suite())
  File "C:\CODE\PYTHON\lib\test\test_support.py", line 187, in run_suite
    raise TestFailed(msg)
test.test_support.TestFailed: errors occurred; run in verbose mode for
details

Why I'm getting a traceback from test_support despite not using regrtest
seems a bit of a mystery.

SKIPPING THE TEST DIRECTORY ENTIRELY
>python ../lib/email/test/test_email.py
... lots of error output ...
Ran 164 tests in 0.770s

FAILED (failures=33, errors=4)


> Another thought just struck me.  Are we certain that the email test
> suite is run when you use regrtest?  I think not!

As above, it certainly is for me, under current 2.3 CVS.

> ...
> So the email regression test (or the email package!) probably has a
> severe Unix dependency (or Windows deficiency :-) that has never been
> detected before.

Barry knows he has cross-platform line-end problems in his test data, but
hasn't wanted to "do something" about that so far.  I'm most unclear now on
why test_email ever worked on Windows; *something* changed very recently,
but don't know what.... lots of error output ...