summaryrefslogtreecommitdiffstats
path: root/Lib/email
Commit message (Collapse)AuthorAgeFilesLines
* #19485: clarify get_param example.R David Murray2013-11-031-1/+1
| | | | Patch by Vajrasky Kok.
* #18324: set_payload now correctly handles binary input.R David Murray2013-08-222-16/+6
| | | | | | | | | | | This also backs out the previous fixes for for #14360, #1717, and #16564. Those bugs were actually caused by the fact that set_payload didn't decode to str, thus rendering the model inconsistent. This fix does mean the data processed by the encoder functions goes through an extra encode/decode cycle, but it means the model is always consistent. Future API updates will provide a better way to encode payloads, which will bypass this minor de-optimization. Tests by Vajrasky Kok.
* Fix a couple of typos.Ezio Melotti2013-08-102-4/+4
|
* #18437: fix comment typo.R David Murray2013-07-131-1/+1
|
* #18431: Decode encoded words in atoms in new email parser.R David Murray2013-07-121-2/+21
| | | | | | There is more to be done here in terms of accepting RFC invalid input that some mailers accept, but this covers the valid RFC places where encoded words can occur in structured headers.
* #18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?=R David Murray2013-07-111-36/+7
| | | | | | | | | | The problem was I was only checking for decimal digits after the third '?', not for *hex* digits :(. This changeset also fixes a couple of comment typos, deletes an unused function relating to encoded word parsing, and removed an invalid 'if' test from the folding function that was revealed by the tests written to validate this issue.
* #18380: pass regex flags to the right argument. Patch by Valentina ↵Ezio Melotti2013-07-061-1/+1
| | | | Mukhamedzhanova.
* #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.
* 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.
* | 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
|\ \ | |/
| * 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.
| * #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.
* | 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
|\ \ | |/
| * #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
|\ \ | |/
| * #16948: Fix quopri encoding of non-latin1 character sets.R David Murray2013-02-052-0/+34
| |
* | #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-182-3/+3
| | | | | | | | Patch by Serhiy Storchaka.
* | 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.
* | #12515: email now registers a defect if the MIME end boundary is missing.R David Murray2012-05-282-3/+14
| | | | | | | | | | | | This commit also restores the news item for 167256 that it looks like Terry inadvertently deleted. (Either that, or I don't understand now merging works...which is equally possible.)
* | #1672568: email now registers defects for base64 payload format errors.R David Murray2012-05-281-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | #14925: email now registers a defect for missing header/body separator.R David Murray2012-05-282-7/+9
| | | | | | | | | | | | | | 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.
* | Make headerregistry fully part of the provisional api.R David Murray2012-05-272-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | When I made the checkin of the provisional email policy, I knew that Address and Group needed to be made accessible from somewhere. The more I looked at it, though, the more it became clear that since this is a provisional API anyway, there's no good reason to hide headerregistry as a private API. It was designed to ultimately be part of the public API, and so it should be part of the provisional API. This patch fully documents the headerregistry API, and deletes the abbreviated version of those docs I had added to the provisional policy docs.
* | Add '__all__' to _encoded_words and mark QByteMap as private.R David Murray2012-05-271-2/+12
| |
* | Recognize '<>' as a special case of an angle-addr in header_value_parser.R David Murray2012-05-261-1/+11
| | | | | | | | | | | | | | Although '<>' is invalid according to RFC 5322, SMTP uses it for various things, and it sometimes ends up in email headers. This patch changes get_angle_addr to recognize it and just register a Defect instead of raising a parsing error.
* | #665194: Add a localtime function to email.utils.R David Murray2012-05-261-0/+53
| | | | | | | | | | | | | | | | Without this function people would be tempted to use the other date functions in email.utils to compute an aware localtime, and those functions are not as good for that purpose as this code. The code is Alexander Belopolsy's from his proposed patch for issue 9527, with a fix (and additional tests) by Brian K. Jones.
* | #12586: Fix a small oversight in the new email policy header setting code.R David Murray2012-05-261-1/+1
| | | | | | | | | | This is a danger of focusing on unit tests: sometimes you forget to do the integration tests.
* | #12586: add provisional email policy with new header parsing and folding.R David Murray2012-05-258-11/+3047
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
generated by cgit v0.12 at 2024-12-12 06:33:24 (GMT)