History log of /external/python/cpython3/Lib/test/test_email/test_parser.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
06ed218ed0020003ac388572fbcf09b88075b664 10-Sep-2016 R David Murray <rdmurray@bitdance.com> #20476: add a message_factory policy attribute to email.
/external/python/cpython3/Lib/test/test_email/test_parser.py
dc1650ca062a99d41a029a6645dc72fd7d820c94 07-Sep-2016 R David Murray <rdmurray@bitdance.com> #22233: Only split headers on \r and/or \n, per email RFCs.

Original patch by Martin Panter, new policy fixes by me.
/external/python/cpython3/Lib/test/test_email/test_parser.py
328cf3cbdfd6b09d4eae496b746e5013291e6aca 15-Nov-2013 Serhiy Storchaka <storchaka@gmail.com> Issue #19590: Use specific asserts in email tests.
/external/python/cpython3/Lib/test/test_email/test_parser.py
80e0aee95b8c4a7da8a1b794793a9e9537d021cf 28-May-2012 R David Murray <rdmurray@bitdance.com> #1672568: email now registers defects for base64 payload format errors.

Which also means that it is now producing *something* for any base64
payload, which is what leads to the couple of older test changes in
test_email. This is a slightly backward incompatible behavior change,
but the new behavior is so much more useful than the old (you can now
*reliably* detect errors, and any program that was detecting errors by
sniffing for a base64 return from get_payload(decode=True) and then doing
its own error-recovery decode will just get the error-recovery decode
right away). So this seems to me to be worth the small risk inherent
in this behavior change.

This patch also refactors the defect tests into a separate test file,
since they are no longer just parser tests.
/external/python/cpython3/Lib/test/test_email/test_parser.py
adbdcdbd9527a3c4000cd4ff0678ff60151f1f79 28-May-2012 R David Murray <rdmurray@bitdance.com> #14925: email now registers a defect for missing header/body separator.

This patch also deprecates the MalformedHeaderDefect. My best guess is that
this defect was rendered obsolete by a refactoring of the parser, and the
corresponding defect for the new parser (which this patch introduces) was
overlooked.
/external/python/cpython3/Lib/test/test_email/test_parser.py
c27e52265b7ff4aa57dc357c289cce8c9dd0fec3 25-May-2012 R David Murray <rdmurray@bitdance.com> #14731: refactor email policy framework.

This patch primarily does two things: (1) it adds some internal-interface
methods to Policy that allow for Policy to control the parsing and folding of
headers in such a way that we can construct a backward compatibility policy
that is 100% compatible with the 3.2 API, while allowing a new policy to
implement the email6 API. (2) it adds that backward compatibility policy and
refactors the test suite so that the only differences between the 3.2
test_email.py file and the 3.3 test_email.py file is some small changes in
test framework and the addition of tests for bugs fixed that apply to the 3.2
API.

There are some additional teaks, such as moving just the code needed for the
compatibility policy into _policybase, so that the library code can import
only _policybase. That way the new code that will be added for email6
will only get imported when a non-compatibility policy is imported.
/external/python/cpython3/Lib/test/test_email/test_parser.py