| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
same boundary as the outer part.
|
| |
|
|
| |
separating boundary for an outer part inside an inner part.
|
| | |
|
| | |
|
| |
|
|
| |
message's end boundary.
|
| |
|
|
| |
argument.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
body. A test message for SF bug #633527.
|
| |
|
|
|
| |
multipart/digest isn't a message/rfc822. This is legal, but counter
to recommended practice in RFC 2046, $5.1.5.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
|
|
(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.
email/test/data is a copy of Lib/test/data. The fate of the latter is
still undecided.
|