summaryrefslogtreecommitdiffstats
path: root/Lib/email
Commit message (Collapse)AuthorAgeFilesLines
...
| * #18380: pass regex flags to the right argument. Patch by Valentina ↵Ezio Melotti2013-07-061-1/+1
| | | | | | | | Mukhamedzhanova.
* | Merge #14360: make encoders.encode_quopri work.R David Murray2013-06-271-2/+6
|\ \ | |/
| * #14360: make encoders.encode_quopri work.R David Murray2013-06-271-2/+6
| | | | | | | | | | | | | | | | | | There were no tests for the encoders module. encode_base64 worked because it is the default and so got tested implicitly elsewhere, and we use encode_7or8bit internally, so that worked, too. I previously fixed encode_noop, so this fix means that everythign in the encoders module now works, hopefully correctly. Also added an explicit test for encode_base64.
* | #11454: Reduce email module load time, improve surrogate check efficiency.R David Murray2013-06-261-4/+10
| | | | | | | | | | | | | | The new _has_surrogates code was suggested by Serhiy Storchaka. See the issue for timings, but it is far faster than any other alternative, and also removes the load time that we previously incurred from compiling the complex regex this replaces.
* | Issue #17516: use comment syntax for comments, instead of multiline stringVictor Stinner2013-03-261-18/+16
| |
* | 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
|\ \ | |/
| * 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-162-1/+5
| | | | | | | | | | | | Initial patch contributed by Edmond Burnett.
* | | Merge with 3.3, issue #17047: remove doubled words added in 3.3,Terry Jan Reedy2013-03-114-4/+4
|\ \ \ | |/ / | | | | | | as reported by Serhiy Storchaka and Matthew Barnett.
| * | Issue #17047: remove doubled words added in 3.3Terry Jan Reedy2013-03-114-4/+4
| | | | | | | | | | | | as reported by Serhiy Storchaka and Matthew Barnett.
* | | Merge: PEP8 fixup on previous patch, remove unused imports in test_email.R David Murray2013-03-071-1/+1
|\ \ \ | |/ /
| * | Merge: PEP8 fixup on previous patch, remove unused imports in test_email.R David Murray2013-03-071-1/+1
| |\ \ | | |/
| | * PEP8 fixup on previous patch, remove unused import in test_email.R David Murray2013-03-072-2/+1
| | |
* | | Merge: #14645: Generator now emits correct linesep for all parts.R David Murray2013-03-071-4/+18
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | | | | Previously the parts of the message retained whatever linesep they had on read, which means if the messages weren't read in univeral newline mode, the line endings could well be inconsistent. In general sending it via smtplib would result in them getting fixed, but it is better to generate them correctly to begin with. Also, the new send_message method of smtplib does not do the fixup, so that method is producing rfc-invalid output without this fix.
| * | Merge: #14645: Generator now emits correct linesep for all parts.R David Murray2013-03-071-4/+18
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | | | | | | | Previously the parts of the message retained whatever linesep they had on read, which means if the messages weren't read in univeral newline mode, the line endings could well be inconsistent. In general sending it via smtplib would result in them getting fixed, but it is better to generate them correctly to begin with. Also, the new send_message method of smtplib does not do the fixup, so that method is producing rfc-invalid output without this fix.
| | * #14645: Generator now emits correct linesep for all parts.R David Murray2013-03-072-4/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the parts of the message retained whatever linesep they had on read, which means if the messages weren't read in univeral newline mode, the line endings could well be inconsistent. In general sending it via smtplib would result in them getting fixed, but it is better to generate them correctly to begin with. Also, the new send_message method of smtplib does not do the fixup, so that method is producing rfc-invalid output without this fix.
* | | #15220: simplify and speed up feedparser's line splitting.R David Murray2013-02-141-18/+9
| | | | | | | | | | | | | | | Original patch submitted by QNX, modified for clarity by me (mostly comments). QNX reports a 30% speed up in average email parsing time.
* | | Merge: #17171: fix email.encoders.encode_7or8bit when applied to binary data.R David Murray2013-02-111-1/+3
|\ \ \ | |/ /
| * | Merge: #17171: fix email.encoders.encode_7or8bit when applied to binary data.R David Murray2013-02-111-1/+3
| |\ \ | | |/
| | * #17171: fix email.encoders.encode_7or8bit when applied to binary data.R David Murray2013-02-112-2/+21
| | |
* | | Merge: #16564: Fix regression in use of encoders.encode_noop with binary data.R David Murray2013-02-092-0/+9
|\ \ \ | |/ /
| * | Merge: #16564: Fix regression in use of encoders.encode_noop with binary data.R David Murray2013-02-092-0/+9
| |\ \ | | |/
| | * #16564: Fix regression in use of encoders.encode_noop with binary data.R David Murray2013-02-093-0/+25
| | |
* | | Merge: #16948: Fix quopri encoding of non-latin1 character sets.R David Murray2013-02-051-0/+13
|\ \ \ | |/ /
| * | Merge: #16948: Fix quopri encoding of non-latin1 character sets.R David Murray2013-02-051-0/+13
| |\ \ | | |/
| | * #16948: Fix quopri encoding of non-latin1 character sets.R David Murray2013-02-052-0/+34
| | |
* | | Merge #16811: Fix folding of headers with no value in provisional policies.R David Murray2013-02-041-1/+1
|\ \ \ | |/ /
| * | #16811: Fix folding of headers with no value in provisional policies.R David Murray2013-02-041-1/+1
| | |
* | | Issue #16714: use 'raise' exceptions, don't 'throw'.Andrew Svetlov2012-12-183-4/+4
|\ \ \ | |/ / | | | | | | Patch by Serhiy Storchaka.
| * | Issue #16714: use 'raise' exceptions, don't 'throw'.Andrew Svetlov2012-12-183-4/+4
| |\ \ | | |/ | | | | | | Patch by Serhiy Storchaka.
| | * Issue #16714: use 'raise' exceptions, don't 'throw'.Andrew Svetlov2012-12-182-3/+3
| | | | | | | | | | | | Patch by Serhiy Storchaka.
* | | utilize yield fromPhilip Jenvey2012-10-012-6/+3
|/ /
* | Closes #15925: fix regression in parsedate() and parsedate_tz() that should ↵Georg Brandl2012-09-222-22/+6
| | | | | | | | return None if unable to parse the argument.
* | Merge #15249: Mangle From lines correctly when body contains invalid bytes.R David Murray2012-08-241-0/+2
|\ \ | |/ | | | | Fix by Colin Su. Test by me, based on a test written by Petri Lehtinen.
| * #15249: Mangle From lines correctly when body contains invalid bytes.R David Murray2012-08-242-1/+17
| | | | | | | | Fix by Colin Su. Test by me, based on a test written by Petri Lehtinen.
* | Issue #665194: Added a small optimizationAlexander Belopolsky2012-08-231-1/+1
| |
* | #665194: fix variable name in exception code path.R David Murray2012-08-231-1/+1
| | | | | | | | | | It was correct in the original patch and I foobared it when I restructured part of the code.
* | #665194: Update email.utils.localtime to use astimezone, and fix bug.R David Murray2012-08-231-29/+22
| | | | | | | | | | | | | | The new code correctly handles historic changes in UTC offsets. A test for this should follow. Original patch by Alexander Belopolsky.
* | Merge #15232: correctly mangle From lines in MIME preamble and epilogueR David Murray2012-07-231-2/+10
|\ \ | |/
| * #15232: correctly mangle From lines in MIME preamble and epilogueR David Murray2012-07-232-2/+32
| |
* | #15160: Extend the new email parser to handle MIME headers.R David Murray2012-06-242-18/+943
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This code passes all the same tests that the existing RFC mime header parser passes, plus a bunch of additional ones. There are a couple of commented out tests where there are issues with the folding. The folding doesn't normally get invoked for headers parsed from source, and the cases are marginal anyway (headers with invalid binary data) so I'm not worried about them, but will fix them after the beta. There are things that can be done to make this API even more convenient, but I think this is a solid foundation worth having. And the parser is a full RFC parser, so it handles cases that the current parser doesn't. (There are also probably cases where it fails when the current parser doesn't, but I haven't found them yet ;) Oh, yeah, and there are some really ugly bits in the parser for handling some 'postel' cases that are unfortunately common. I hope/plan to to eventually refactor a lot of the code in the parser which should reduce the line count...but there is no escaping the fact that the error recovery is welter of special cases.
* | Issue #14653: email.utils.mktime_tz() no longer relies on systemAlexander Belopolsky2012-06-221-4/+4
|\ \ | |/ | | | | mktime() when timezone offest is supplied.
| * Issue #14653: email.utils.mktime_tz() no longer relies on systemAlexander Belopolsky2012-06-222-4/+10
| | | | | | | | mktime() when timezone offest is supplied.
* | Merge: Update out of date docstring.R David Murray2012-06-171-7/+5
|\ \ | |/
| * Update out of date docstring.R David Murray2012-06-171-7/+5
| |
* | Now that Defects are Exception subclasses, call super.R David Murray2012-06-091-0/+5
| | | | | | | | | | | | | | | | The behavior of MessageDefect is legacy behavior. The chances anyone is actually using the undocumented 'line' attribute is low, but it costs little to retain backward compatibility. Although one of the costs is having to restore normal exception behavior in HeaderDefect. On the other hand, I'll probably add some specialized behavior there later.
* | #1079: Fix parsing of encoded words.R David Murray2012-06-021-4/+41
| | | | | | | | | | | | | | | | | | This is a behavior change: before this leading and trailing spaces were stripped from ASCII parts, now they are preserved. Without this fix we didn't parse the examples in the RFC correctly, so I think breaking backward compatibility here is justified. Patch by Ralf Schlatterbeck.
* | Don't use metaclasses when class decorators can do the job.R David Murray2012-05-312-26/+22
| | | | | | | | | | Thanks to Nick Coghlan for pointing out that I'd forgotten about class decorators.
* | #10839: raise an error on add of duplicate unique headers in new email policiesR David Murray2012-05-293-0/+37
| | | | | | | | | | | | | | | | | | | | | | This feature was supposed to be part of the initial email6 checkin, but it got lost in my big refactoring. In this patch I'm not providing an easy way to turn off the errors, but they only happen when a header is added programmatically, and it is almost never the right thing to do to allow the duplicate to be added. An application that needs to add duplicates of unique headers can create a policy subclass to allow it.
generated by cgit v0.12 at 2025-04-23 02:15:09 (GMT)