summaryrefslogtreecommitdiffstats
path: root/Lib/email/_encoded_words.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-27397: Make email module properly handle invalid-length base64 strings ↵Tal Einat2018-06-121-18/+30
| | | | | | | (#7583) When attempting to base64-decode a payload of invalid length (1 mod 4), properly recognize and handle it. The given data will be returned as-is, i.e. not decoded, along with a new defect, InvalidBase64LengthDefect.
* Fixed a type error introduced in issue #28992.Serhiy Storchaka2016-12-211-1/+1
|
* Issue #28992: Use bytes.fromhex().Serhiy Storchaka2016-12-211-1/+1
|
* Escaped backslashes in docstrings.Serhiy Storchaka2015-04-031-1/+1
|
* Issue #17047: remove doubled words added in 3.3Terry Jan Reedy2013-03-111-1/+1
| | | | as reported by Serhiy Storchaka and Matthew Barnett.
* Add '__all__' to _encoded_words and mark QByteMap as private.R David Murray2012-05-271-2/+12
|
* #12586: add provisional email policy with new header parsing and folding.R David Murray2012-05-251-0/+211
When the new policies are used (and only when the new policies are explicitly used) headers turn into objects that have attributes based on their parsed values, and can be set using objects that encapsulate the values, as well as set directly from unicode strings. The folding algorithm then takes care of encoding unicode where needed, and folding according to the highest level syntactic objects. With this patch only date and time headers are parsed as anything other than unstructured, but that is all the helper methods in the existing API handle. I do plan to add more parsers, and complete the set specified in the RFC before the package becomes stable.