summaryrefslogtreecommitdiffstats
path: root/Lib/email
Commit message (Collapse)AuthorAgeFilesLines
* _parsegen(): Add a missing check for NeedMoreData.Barry Warsaw2004-05-151-0/+3
|
* forward porting from release23-maintBarry Warsaw2004-05-131-0/+10
|
* test_boundary_in_non_multipart(): Added a test for SF bug # 846938.Barry Warsaw2004-05-131-0/+15
|
* encode_7or8bit(): Clearing out some old patches; iso-2202 is non-ASCII butBarry Warsaw2004-05-131-5/+10
| | | | still 7-bit.
* readline(): RFC 2046, section 5.1.2 (and partially 5.1) both state that theBarry Warsaw2004-05-131-3/+5
| | | | | | | | | | parser must recognize outer boundaries in inner parts. So cruise through the EOF stack backwards testing each predicate against the current line. There's still some discussion about whether this is (always) the best thing to do. Anthony would rather parse these messages as if the outer boundaries were ignored. I think that's counter to the RFC, but might be practically more useful. Can you say behavior flag? (ug).
* test_nested_inner_contains_outer_boundary(), test_nested_with_same_boundary():Barry Warsaw2004-05-131-0/+36
| | | | Two evil samples from Anthony's MIME torture tests.
* _structure(): Make sure all output goes the to fp object.Barry Warsaw2004-05-131-2/+2
|
* Another evil test from Anthony's suite. This one has an inner part with theBarry Warsaw2004-05-131-0/+83
| | | | same boundary as the outer part.
* A boiled down example from Anthony's MIME torture tests. This one has aBarry Warsaw2004-05-131-0/+101
| | | | separating boundary for an outer part inside an inner part.
* Tests for message/external-body and for duplicate boundary lines.Barry Warsaw2004-05-111-3/+12
|
* More boiled down tests from Anthony's big torture suite.Barry Warsaw2004-05-111-2/+26
|
* A boiled down message/external-body example from Anthony's torture test.Barry Warsaw2004-05-111-0/+40
|
* An example with multiple boundary lines.Barry Warsaw2004-05-111-0/+22
|
* _parsegen(): Move the message/rfc822 clause to after theBarry Warsaw2004-05-111-12/+13
| | | | | | message/delivery-status clause, and genericize it to handle all (other) message/* content types. This lets us correctly parse 2 more of Anthony's MIME torture tests (specifically, the message/external-body examples).
* _parsegen(): Watch out for empty epilogues.Barry Warsaw2004-05-111-4/+5
|
* _parse_headers(): Strip a trailing newline from the envelope header. ClosesBarry Warsaw2004-05-101-0/+4
| | | | SF #951088.
* _split_ascii(): Small optimization by RH.Barry Warsaw2004-05-101-1/+1
|
* SF patch # 884030 by Amit Aronovitch; fixes the _subpart argument to matchBarry Warsaw2004-05-091-5/+7
| | | | documented semantics.
* test_mime_attachments_in_constructor(): New test to check for SF bug # 884030.Barry Warsaw2004-05-091-0/+9
|
* we dont support any Python's before 2.3 now.Barry Warsaw2004-05-092-139/+0
|
* Update to Python 2.3, getting rid of backward compatiblity crud.Barry Warsaw2004-05-095-84/+19
|
* Update to Python 2.3, getting rid of backward compatiblity crud.Barry Warsaw2004-05-091-281/+20
| | | | This Parser is now just a backward compatible front-end to the FeedParser.
* Update to Python 2.3, getting rid of backward compatiblity crud.Barry Warsaw2004-05-091-28/+17
|
* Update to Python 2.3, getting rid of backward compatiblity crud. We don'tBarry Warsaw2004-05-091-10/+52
| | | | need the _compat21 or _compat22 modules either.
* Update to Python 2.3, getting rid of backward compatiblity crud. Get rid of aBarry Warsaw2004-05-091-27/+6
| | | | bunch of module globals that aren't used.
* Update to Python 2.3, getting rid of backward compatiblity crud. Get rid of aBarry Warsaw2004-05-091-57/+29
| | | | | | | | | bunch of module globals that aren't used. __maxheaderlen -> _maxheaderlen _handle_multipart(): This should be more RFC compliant now, and does match the updated/fixed semantics for preamble and epilogue.
* An updated FeedParser that should be RFC complaint, passes all existingBarry Warsaw2004-05-091-289/+359
| | | | | | (standard) tests, and doesn't throw parse errors. I still need throw Anthony's torture test at it, but I wanted to get this checked in and off my disk.
* Add MessageDefect and subclasses.Barry Warsaw2004-05-091-4/+27
|
* Update to Python 2.3, getting rid of backward compatiblity crud.Barry Warsaw2004-05-091-16/+7
|
* Like msg_12.txt but with some extra vertical whitespace around the innerBarry Warsaw2004-05-091-0/+38
| | | | message's end boundary.
* A bunch of new tests, and updated tests for the email 3.0 FeedParser.Barry Warsaw2004-05-091-63/+189
|
* New parser. Next up, making the current parser use this parserAnthony Baxter2004-03-221-0/+362
|
* test_email: comment out two fail-test cases that no longer fail with the newThomas Wouters2004-03-201-25/+27
| | | | | parser -- for now. Failure behaviour of the new parser(s) will change in any case, so this will be revisited later anyway.
* Merge in Anthony's new parser code, from the anthony-parser-branch:Thomas Wouters2004-03-201-128/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > ---------------------------- > revision 1.20.4.4 > date: 2003/06/12 09:14:17; author: anthonybaxter; state: Exp; lines: +13 -6 > preamble is None when missing, not ''. > Handle a couple of bogus formatted messages - now parses my main testsuite. > Handle message/external-body. > ---------------------------- > revision 1.20.4.3 > date: 2003/06/12 07:16:40; author: anthonybaxter; state: Exp; lines: +6 -4 > epilogue-processing is now the same as the old parser - the newline at the > end of the line with the --endboundary-- is included as part of the epilogue. > Note that any whitespace after the boundary is _not_ part of the epilogue. > ---------------------------- > revision 1.20.4.2 > date: 2003/06/12 06:39:09; author: anthonybaxter; state: Exp; lines: +6 -4 > message/delivery-status fixed. > HeaderParser fixed. > ---------------------------- > revision 1.20.4.1 > date: 2003/06/12 06:08:56; author: anthonybaxter; state: Exp; lines: +163 -129 > A work-in-progress snapshot of the new parser. A couple of known problems: > > - first (blank) line of MIME epilogues is being consumed > - message/delivery-status isn't quite right > > It still needs a lot of cleanup, but right now it parses a whole lot of > badness that the old parser failed on. I also need to think about adding > back the old 'strict' flag in some way. > =============================================================================
* Add CJK codecs support as discussed on python-dev. (SF #873597)Hye-Shik Chang2004-01-171-7/+0
| | | | | Several style fixes are suggested by Martin v. Loewis and Marc-Andre Lemburg. Thanks!
* Fixes to support CJKCodecs as per SF bug #852347. Actually, thisBarry Warsaw2003-12-301-19/+16
| | | | | | | | | | | patch removes dependencies on the old unsupported KoreanCodecs package and the alternative JapaneseCodecs package. Since both of those provide aliases for their codecs, this removal just makes the generic codec names work. We needed to make slight changes to __init__() as well. This will be backported to Python 2.3 when its branch freeze is over.
* Bump version number to 2.5.5Barry Warsaw2003-12-301-1/+1
|
* __init__(): The docstring was incorrect regarding how header wrappingBarry Warsaw2003-11-191-5/+4
| | | | | | gets done when maxheaderlen <> 0. The header really gets wrapped via the email.Header.Header class, which has a more sophisticated algorithm than just splitting on semi-colons.
* Fix a bunch of typos in documentation, docstrings and comments.Walter Dörwald2003-10-201-1/+1
| | | | (From SF patch #810751)
* test_get_param_with_semis_in_quotes(): Test case for SF bug #794466.Barry Warsaw2003-09-031-0/+7
| | | | Backport candidate.
* A fix for parsing parameters when there are semicolons inside theBarry Warsaw2003-09-031-1/+18
| | | | | | | | | | | quotes. Fixes SF bug #794466, with the essential patch provided by Stuart D. Gathman. Specifically, _parseparam(), _get_params_preserve(): Use the parsing function that takes quotes into account, as given (essentially) in the bug report's test program. Backport candidate.
* Bump the version number for the standalone mimelib package.Barry Warsaw2003-08-191-1/+1
|
* test_rfc2231_no_language_or_charset_in_filename(),Barry Warsaw2003-08-191-0/+37
| | | | | | | | | test_rfc2231_no_language_or_charset_in_boundary(), test_rfc2231_no_language_or_charset_in_charset(): New tests for proper decoding of some RFC 2231 headers. Backport candidate (as was the Utils.py 1.25 change) to both Python 2.3.1 and 2.2.4 -- will do momentarily.
* get_param(): Update the docstring to explain how CHARSET and LANGUAGEBarry Warsaw2003-08-191-7/+12
| | | | | | | | | | can be None, and what to do in that situation. get_filename(), get_boundary(), get_content_charset(): Make sure these handle RFC 2231 headers without a CHARSET field. Backport candidate (as was the Utils.py 1.25 change) to both Python 2.3.1 and 2.2.4 -- will do momentarily.
* decode_rfc2231(): We need to urllib.unquote() the value even if theBarry Warsaw2003-08-191-1/+1
| | | | | | charset and language fields are not present, e.g. as in: title*0="This%20is%20encoded"
* _make_boundary(): A minor optimization suggested by the Timbot.Barry Warsaw2003-06-241-1/+1
|
* AddressList.__str__(): Get rid of useless, and broken method. ClosesBarry Warsaw2003-06-131-3/+0
| | | | SF #753617. Back port candidate (but low priority).
* get_payload(): Improve the TypeError message when the payload isn't ofBarry Warsaw2003-06-101-1/+1
| | | | the expected type. In response to SF #751451.
* _make_boundary(): Fix for SF bug #745478, broken boundary calculationBarry Warsaw2003-05-292-3/+7
| | | | | | | | | in some locales. This code simplifies the boundary algorithm to use randint() which is what we wanted anyway. Bump package version to 2.5.3. Backport candidate for Python 2.2.3
* Bump version numberBarry Warsaw2003-05-081-1/+1
|
generated by cgit v0.12 at 2024-10-22 01:52:39 (GMT)