| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Update tests for email 2.5.
|
|
|
|
|
|
|
|
|
|
|
|
| |
because the test file, msg_26.txt which has \r\n line endings, was
getting munged by cvs, which knows to do line ending conversions for
text files. But we want \r\n to be preserved on all platforms, so we
cvs admin'd the file to be -kb (binary), which means we have to open
the file in binary mode to preserve these line ends. Hopefully this
will be the end of the thrashing on this issue (but probably not).
Test passes on *nix now, and Tim confirms it passes on Windows. We'll
leave it to Jack to test MacOS.
|
|
|
|
| |
bug #648119.
|
|
|
|
|
|
| |
file, needed because some binary distros (read RPMs) don't include the
test module in their standard Python package. This eliminates an
external dependency and closes SF bug # 650441.
|
|
|
|
|
| |
and the day number in an RFC 2822 date specification. See bug
#552345.
|
|
|
|
| |
RFC 2822's rules w.r.t. dots in the realname part of address fields.
|
|
|
|
|
|
| |
separating blank line between a header block and body text.
Tests both lax and strict parsing.
|
|
|
|
|
| |
#631350, where a subobject in a multipart/digest isn't a
message/rfc822.
|
|
|
|
| |
one that tests the obscure bug reported in SF # 625509.
|
| |
|
| |
|
|
|
|
| |
default get_body_encoding() cannot be SHORTEST.
|
|
|
|
|
|
| |
the change in revision 1.11 (test_email.py) in response to SF bug
#609988. We now think that was the wrong fix and that WinZip was the
real culprit there.
|
| |
|
|
|
|
|
|
|
|
| |
Python 2.1.3. However it's required by the email tests suite, so poke
it into the encodings aliases if it's missing. The is apparently the
approved API for doing so.
Now we can remove the hexversion shortcircuits in the test suite.
|
|
|
|
|
| |
doesn't know about the ansi-x3.4-1968 charset so skip two tests that
rely on that (msg_32.txt and msg_33.txt).
|
|
|
|
| |
some of the test values which change because of this.
|
|
|
|
| |
controversy.
|
|
|
|
|
|
|
| |
project, and with assistance from Oleg Broytmann. Specifically,
added some new tests to make sure we handle RFC 2231 encoded
parameters correctly. Two new data files were added which contain RFC
2231 encoded parameters.
|
|
|
|
| |
failures on Windows. Closes SF bug # 609988.
|
|
|
|
| |
de-backslash-ifying.
|
|
|
|
| |
broken wrapping of long ASCII headers.
|
|
|
|
| |
Oleg Broytmann in SF patch #600096. Whitespace normalized by Barry.
|
| |
|
| |
|
| |
|
|
|
|
| |
email 2.2 but fails in email 1.0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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. :)
|
|
(i.e. email.test), so move the guts of them here from Lib/test. The
latter directory will retain stubs to run the email.test tests using
Python's standard regression test.
test_email_torture.py is a torture tester which will not run under
Python's test suite because I don't want to commit megs of data to
that project (it will fail cleanly there). When run under the mimelib
project it'll stress test the package with megs of message samples
collected from various locations in the wild.
|