| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
nonsense.
Resolve SF bug 1409403: email.Message should supress warning from uu.decode.
|
|
|
|
| |
3.0/Python 2.4.
|
| |
|
| |
|
|
|
|
|
| |
Change headerRE as suggested in the bug report, so that single character
headers are accepted. Test case added too. Backported from the trunk.
|
|
|
|
|
|
|
|
|
|
|
| |
SF bug #1403349 solution for email 3.0; some MUAs use the 'file' parameter
name in the Content-Distribution header, so Message.get_filename() should fall
back to using that.
Also, bump the email package version to 3.0.1 for eventual release. Of
course, add a test case too.
XXX Need to update the documentation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
caused by a self._input.readline() call that wasn't checking for the
NeedsMoreData marker.
msg_43.txt contains a message that illustrates the problem, when
email.message_from_*() is called. That interface uses the Parser API, which
splits reads into 8192 byte chunks. It so happens that for the test message,
the 8192 chunk falls inside a message/delivery-status, which is where in the
FeedParser the readline() call was that didn't check for NeedsMoreData.
I also added an assert to unreadline() so it'll be more evident if an attempt
to push back NeedsMoreData ever happens again.
Bump the email package version number.
|
|
|
|
| |
this, and add test cases.
|
|
|
|
|
|
|
|
|
| |
in a newline, and it's an end boundary, the FeedParser wasn't recognizing it
as such. Tweak the regexp to make the ending linesep optional.
For grins, clear self._partial when closing the BufferedSubFile.
Added a test case.
|
|
|
|
|
|
| |
says boundaries may begin -- but not end -- with whitespace.
I will backport to Python 2.3.
|
|
|
|
|
| |
used to replace rfc822.formatdate for protocols like HTTP (where 'GMT' must
be the timezone string).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Briefly (from the NEWS file):
- Updates for the email package:
+ All deprecated APIs that in email 2.x issued warnings have been removed:
_encoder argument to the MIMEText constructor, Message.add_payload(),
Utils.dump_address_pair(), Utils.decode(), Utils.encode()
+ New deprecations: Generator.__call__(), Message.get_type(),
Message.get_main_type(), Message.get_subtype(), the 'strict' argument to
the Parser constructor. These will be removed in email 3.1.
+ Support for Python earlier than 2.3 has been removed (see PEP 291).
+ All defect classes have been renamed to end in 'Defect'.
+ Some FeedParser fixes; also a MultipartInvariantViolationDefect will be
added to messages that claim to be multipart but really aren't.
+ Updates to documentation.
|
|
|
|
| |
del_param fails when specifying a header.
|
|
|
|
|
|
|
|
|
| |
Specifically, time.strftime() no longer accepts a 0 in the yday position of a
time tuple, since that can crash some platform strftime() implementations.
parsedate_tz(): Change the return value to return 1 in the yday position.
Update tests in test_rfc822.py and test_email.py
|
|
|
|
|
|
|
|
|
|
| |
\r\n only get the \n stripped, not the \r (unless it's the last header which
does get the \r stripped). Patch by Tony Meyer.
test_whitespace_continuation_last_header(),
test_strip_line_feed_and_carriage_return_in_headers(): New tests.
_parse_headers(): Be sure to strip \r\n from the right side of header lines.
|
| |
|
|
|
|
| |
Two evil samples from Anthony's MIME torture tests.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
parser -- for now. Failure behaviour of the new parser(s) will change in any
case, so this will be revisited later anyway.
|
|
|
|
| |
Backport candidate.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
argument.
|
|
|
|
| |
Content-Transfer-Encoding: x-uuencode
|
| |
|
| |
|
| |
|
|
|
|
| |
module when decoding a message with broken base64.
|
| |
|
|
|
|
| |
from Jason Mastaler :)
|
|
|
|
| |
both the charset and language without including any single quotes.
|
| |
|
| |
|
|
|
|
|
| |
Received headers (first on semis then on whitespace), given by Jason
Mastaler.
|
|
|
|
| |
SF # 640110.
|
| |
|
|
|
|
| |
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.
|