| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
I have compared output between pre- and post-patch runs of these tests
to make sure there's nothing missing and nothing broken, on both
Windows and Linux. The only differences I found were actually tests
that were previously *not* run.
|
| |
|
| |
|
|
|
|
|
| |
self.assertEqual(x, y). (Christian used self.failUnlessEqual(),
but the double negative makes it hard to grok, so I changed it.)
|
|
|
|
|
| |
normal code (or drop them if they only repeat previous
tests).
|
| |
|
|
|
|
| |
(Rough first cut.)
|
|
|
|
|
|
|
|
|
|
|
| |
imports e.g. test_support must do so using an absolute package name
such as "import test.test_support" or "from test import test_support".
This also updates the README in Lib/test, and gets rid of the
duplicate data dirctory in Lib/test/data (replaced by
Lib/email/test/data).
Now Tim and Jack can have at it. :)
|
| |
|
|
|
|
|
| |
allows using the tests with unittest.py as a script. The tests will
still run when run as a script themselves.
|
|
|
|
|
| |
based on a suggestion from Tim Peters; also make sure that we're really
doing exponentiation and not multiplication.
|
|
|
|
|
| |
are auto-coerced to longs now, but this test still expected OverflowError.
I can't imagine this test failure was unique to Windows.
|
|
|