| Commit message (Expand) | Author | Age | Files | Lines |
* | decode_rfc2231(): As Christian Robottom Reis points out, it makes no sense to | Barry Warsaw | 2006-10-04 | 1 | -4/+0 |
|
|
* | Forward port some fixes that were in email 2.5 but for some reason didn't make | Barry Warsaw | 2006-07-26 | 3 | -1/+100 |
|
|
* | More RFC 2231 improvements for the email 4.0 package. As Mark Sapiro rightly | Barry Warsaw | 2006-07-21 | 3 | -41/+277 |
|
|
* | decode_rfc2231(): Be more robust against buggy RFC 2231 encodings. | Barry Warsaw | 2006-07-17 | 3 | -4/+43 |
|
|
* | Port forward from 2.4 branch: | Barry Warsaw | 2006-05-01 | 3 | -0/+13 |
|
|
* | The email module's parsedate_tz function now sets the daylight savings | Anthony Baxter | 2006-04-03 | 3 | -5/+6 |
|
|
* | whitespace n11n | Anthony Baxter | 2006-03-20 | 1 | -8/+8 |
|
|
* | Merge email package 4.0 from the sandbox, including documentation, test cases, | Barry Warsaw | 2006-03-18 | 27 | -202/+3562 |
|
|
* | Actually this file should have svn:eol-style CRLF since it's specifically | Barry Warsaw | 2006-03-04 | 1 | -45/+45 |
|
|
* | Set eol-style to native -- doesn't appear to be any reason | Tim Peters | 2006-03-04 | 1 | -45/+45 |
|
|
* | Port relevant patches for SF 1409455 to the trunk for email 3.0/Python 2.5. | Barry Warsaw | 2006-02-08 | 5 | -8/+20 |
|
|
* | Resolves SF bug #1423972. | Barry Warsaw | 2006-02-04 | 1 | -2/+4 |
|
|
* | parsedate_tz(): Minor cleanup. | Barry Warsaw | 2006-02-03 | 2 | -3/+11 |
|
|
* | SF bug #1347874; FeedParser does not comply with RFC2822. | Barry Warsaw | 2006-01-17 | 2 | -2/+11 |
|
|
* | Ported 42075 from release23-maint branch. | Barry Warsaw | 2006-01-17 | 4 | -5/+51 |
|
|
* | fix broken (unexecuted) test | Anthony Baxter | 2005-06-08 | 1 | -3/+3 |
|
|
* | Fixes for SF #1076485, which I'll apply to the CVS head too. The problem was | Barry Warsaw | 2004-12-05 | 4 | -4/+274 |
|
|
* | RFC 2822 describes the characters allowed in a header field name. Conform to | Barry Warsaw | 2004-11-29 | 2 | -1/+19 |
|
|
* | There's likely nothing more to do to the email package before Python 2.4 is | Barry Warsaw | 2004-11-29 | 1 | -1/+1 |
|
|
* | Fix for SF bug #1072623. When the last line of the input string does not end | Barry Warsaw | 2004-11-28 | 2 | -1/+16 |
|
|
* | get_boundary(): Fix for SF bug #1060941. RFC 2046 says boundaries may begin | Barry Warsaw | 2004-11-06 | 1 | -1/+2 |
|
|
* | test_boundary_with_leading_space(): Test case for SF bug #1060941. RFC 2046 | Barry Warsaw | 2004-11-06 | 1 | -0/+19 |
|
|
* | Whitespace normalization. | Tim Peters | 2004-10-12 | 1 | -1/+1 |
|
|
* | Added a usegmt flag to email.Utils.formatdate - this allows it to be | Anthony Baxter | 2004-10-11 | 2 | -2/+18 |
|
|
* | All known bugs are closed, and Python 2.4b1 is coming out soon, so bump | Barry Warsaw | 2004-10-09 | 1 | -1/+1 |
|
|
* | Fix SF bug # 1030941. In _parsegen(), in the clause where we're | Barry Warsaw | 2004-10-09 | 1 | -3/+7 |
|
|
* | An example message for SF bug # 1030941. | Barry Warsaw | 2004-10-09 | 1 | -0/+20 |
|
|
* | test_missing_start_boundary(): A test for SF bug # 1030941. | Barry Warsaw | 2004-10-09 | 1 | -0/+15 |
|
|
* | __init__(): Coerce the input_charset to unicode (with ascii encoding) before | Barry Warsaw | 2004-10-09 | 1 | -2/+3 |
|
|
* | Fix test for FeedParser results. | Barry Warsaw | 2004-10-03 | 1 | -2/+2 |
|
|
* | as_string(): Indicate that this mangles From_ lines. | Barry Warsaw | 2004-10-03 | 1 | -1/+2 |
|
|
* | Big email 3.0 API changes, with updated unit tests and documentation. | Barry Warsaw | 2004-10-03 | 24 | -371/+230 |
|
|
* | Test cases and fixes for bugs described in patch #873418: email/Message.py: | Barry Warsaw | 2004-08-16 | 2 | -2/+14 |
|
|
* | Resolution of bug #997368, "strftime() backward compatibility". | Barry Warsaw | 2004-08-07 | 2 | -3/+3 |
|
|
* | Resolution of SF bug #1002475 and patch #1003693; Header lines that end in | Barry Warsaw | 2004-08-07 | 2 | -3/+33 |
|
|
* | _parsegen(): Add a missing check for NeedMoreData. | Barry Warsaw | 2004-05-15 | 1 | -0/+3 |
|
|
* | forward porting from release23-maint | Barry Warsaw | 2004-05-13 | 1 | -0/+10 |
|
|
* | test_boundary_in_non_multipart(): Added a test for SF bug # 846938. | Barry Warsaw | 2004-05-13 | 1 | -0/+15 |
|
|
* | encode_7or8bit(): Clearing out some old patches; iso-2202 is non-ASCII but | Barry Warsaw | 2004-05-13 | 1 | -5/+10 |
|
|
* | readline(): RFC 2046, section 5.1.2 (and partially 5.1) both state that the | Barry Warsaw | 2004-05-13 | 1 | -3/+5 |
|
|
* | test_nested_inner_contains_outer_boundary(), test_nested_with_same_boundary(): | Barry Warsaw | 2004-05-13 | 1 | -0/+36 |
|
|
* | _structure(): Make sure all output goes the to fp object. | Barry Warsaw | 2004-05-13 | 1 | -2/+2 |
|
|
* | Another evil test from Anthony's suite. This one has an inner part with the | Barry Warsaw | 2004-05-13 | 1 | -0/+83 |
|
|
* | A boiled down example from Anthony's MIME torture tests. This one has a | Barry Warsaw | 2004-05-13 | 1 | -0/+101 |
|
|
* | Tests for message/external-body and for duplicate boundary lines. | Barry Warsaw | 2004-05-11 | 1 | -3/+12 |
|
|
* | More boiled down tests from Anthony's big torture suite. | Barry Warsaw | 2004-05-11 | 1 | -2/+26 |
|
|
* | A boiled down message/external-body example from Anthony's torture test. | Barry Warsaw | 2004-05-11 | 1 | -0/+40 |
|
|
* | An example with multiple boundary lines. | Barry Warsaw | 2004-05-11 | 1 | -0/+22 |
|
|
* | _parsegen(): Move the message/rfc822 clause to after the | Barry Warsaw | 2004-05-11 | 1 | -12/+13 |
|
|
* | _parsegen(): Watch out for empty epilogues. | Barry Warsaw | 2004-05-11 | 1 | -4/+5 |
|
|