summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_email/test_contentmanager.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-41402: Fix email ContentManager calling .encode() on bytes (GH-21631)Johannes Reiff2021-08-091-0/+12
|
* bpo-40597: Allow email.contextmanager set_content() to set a null string. ↵Mark Sapiro2020-07-081-0/+13
| | | | (GH-20542)
* bpo-40597: email: Use CTE if lines are longer than max_line_length ↵Arkadiusz Hiler2020-05-141-0/+15
| | | | | | | | | | | | | | | consistently (gh-20038) raw_data_manager (default for EmailPolicy, EmailMessage) does correct wrapping of 'text' parts as long as the message contains characters outside of 7bit US-ASCII set: base64 or qp Content-Transfer-Encoding is applied if the lines would be too long without it. It did not, however, do this for ascii-only text, which could result in lines that were longer than policy.max_line_length or even the rfc 998 maximum. This changeset fixes the heuristic so that if lines are longer than policy.max_line_length, it will always apply a content-transfer-encoding so that the lines are wrapped correctly.
* Issue #27076: Doc, comment and tests spelling fixesMartin Panter2016-05-261-1/+1
| | | | Most fixes to Doc/ and Lib/ directories by Ville Skyttä.
* Merge #19772: Do not mutate message when downcoding to 7bit.R David Murray2014-02-081-1/+1
|
* #20531: Revert e20f98a8ed71, the 3.4 version of the #19063 fix.R David Murray2014-02-071-2/+3
|
* #19063: fix set_payload handling of non-ASCII string input.R David Murray2013-12-111-3/+2
| | | | | This version of the fix raises an error instead of accepting the invalid input (ie: if a non-ASCII string is used but no charset is specified).
* #18891: Complete new provisional email API.R David Murray2013-10-171-0/+796
This adds EmailMessage and, MIMEPart subclasses of Message with new API methods, and a ContentManager class used by the new methods. Also a new policy setting, content_manager. Patch was reviewed by Stephen J. Turnbull and Serhiy Storchaka, and reflects their feedback. I will ideally add some examples of using the new API to the documentation before the final release.