summaryrefslogtreecommitdiffstats
path: root/Lib/email/parser.py
Commit message (Collapse)AuthorAgeFilesLines
* #20476: use EmailMessage as factory if non-compat32 policy is used.R David Murray2014-02-071-1/+1
| | | | | In 3.5 I will fix this right by adding a message_factory attribute to the policy.
* Add missing FeedParser and BytesFeedParser to email.parser.__all__.R David Murray2013-03-161-1/+2
|
* Merge: #17431: Fix missing import of BytesFeedParser in email.parser.R David Murray2013-03-161-1/+1
|\
| * #17431: Fix missing import of BytesFeedParser in email.parser.R David Murray2013-03-161-1/+1
| | | | | | | | Initial patch contributed by Edmond Burnett.
| * #11686: add missing entries to email __all__ lists.R David Murray2012-03-171-1/+1
| | | | | | | | Original patch by Steffen Daode Nurpmeso
* | #14731: refactor email policy framework.R David Murray2012-05-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | #11731: simplify/enhance parser/generator API by introducing policy objects.R David Murray2011-04-181-2/+9
| | | | | | | | | | | | | | | | This new interface will also allow for future planned enhancements in control over the parser/generator without requiring any additional complexity in the parser/generator API. Patch reviewed by Éric Araujo and Barry Warsaw.
* | #11684: Complete parser bytes interface by adding BytesHeaderParserR David Murray2011-04-131-1/+9
| | | | | | | | Patch by Steffen Daode Nurpmeso.
* | Remove the 'strict' argument to Parser, deprecated since 2.4.R David Murray2011-03-291-22/+2
|/
* Properly close a temporary TextIOWrapper in 'email'.Brett Cannon2010-10-291-1/+2
|
* #4661: add bytes parsing and generation to email (email version bump to 5.1.0)R. David Murray2010-10-081-1/+45
| | | | | | | | The work on this is not 100% complete, but everything is present to allow real-world testing of the code. The only remaining major todo item is to (hopefully!) enhance the handling of non-ASCII bytes in headers converted to unicode by RFC2047 encoding them rather than replacing them with '?'s.
* Patch for issue 2848, mostly by Humberto Diogenes, with a couple ofBarry Warsaw2008-06-121-5/+1
| | | | small fixes by Barry. This removes mimetools from the stdlib.
* Copying the email package back, despite its failings.Guido van Rossum2007-08-301-0/+95
|
* Remove the email package for now.Guido van Rossum2007-08-251-91/+0
| | | | | | Once Barry and the email-sig have a working new version we'll add it back. If it doesn't make the 3.0a deadline (release August 31), too bad.
* SF patch# 1770008 by Christian Heimes (plus some extras).Guido van Rossum2007-08-091-1/+1
| | | | | | | | | | Completely get rid of StringIO.py and cStringIO.c. I had to fix a few tests and modules beyond what Christian did, and invent a few conventions. E.g. in elementtree, I chose to write/return Unicode strings whe no encoding is given, but bytes when an explicit encoding is given. Also mimetools was made to always assume binary files.
* Merge p3yk branch with the trunk up to revision 45595. This breaks a fairThomas Wouters2006-04-211-0/+91
number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
generated by cgit v0.12 at 2024-11-11 02:40:37 (GMT)