summaryrefslogtreecommitdiffstats
path: root/Doc/library/email.headerregistry.rst
Commit message (Collapse)AuthorAgeFilesLines
* [3.13] docs: module page titles should not start with a link to themselves ↵Miss Islington (bot)2024-05-081-2/+2
| | | | | | | | (GH-117099) (#118790) docs: module page titles should not start with a link to themselves (GH-117099) (cherry picked from commit bcb435ee8ff41b5ec5d879ee0b6651f146a66151) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
* Docs: Fix backtick errors found by sphinx-lint (#97998)Hugo van Kemenade2022-10-071-1/+1
| | | Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
* gh-71223: Improve rendering of some references in the docs (GH-93041)Serhiy Storchaka2022-05-211-1/+1
| | | | For example, instead of "eval()uated" (link from "eval()") show "evaluated" (link from the whole word).
* bpo-42770: Fix a typo in the email.headerregistry docs (GH-23982)Zackery Spytz2020-12-291-1/+1
| | | Automerge-Triggered-By: GH:zware
* bpo-35805: Add parser for Message-ID email header. (GH-13397)Abhilash Raj2019-06-041-13/+20
| | | | | | | | | | | | | * bpo-35805: Add parser for Message-ID header. This parser is based on the definition of Identification Fields from RFC 5322 Sec 3.6.4. This should also prevent folding of Message-ID header using RFC 2047 encoded words and hence fix bpo-35805. * Prevent folding of non-ascii message-id headers. * Add fold method to MsgID token to prevent folding.
* bpo-37116: Use PEP 570 syntax for positional-only parameters. (GH-13700)Serhiy Storchaka2019-06-011-1/+1
|
* Fix typos in multiple `.rst` files (#1668)delirious-lettuce2017-05-191-1/+1
|
* 24277: Make it clearer that the new modules are not provisional.R David Murray2016-09-081-3/+7
| | | | | Also make it clear on the contents page what chapters are about the legacy API.
* #24277: The new email API is no longer provisional.R David Murray2016-09-081-24/+19
| | | | | | | This is a wholesale reorganization and editing of the email documentation to make the new API the standard one, and the old API the 'legacy' one. The default is still the compat32 policy, for backward compatibility. We will change that eventually.
* Issue #22558: Add remaining doc links to source code for Python-coded modules.Terry Jan Reedy2016-06-111-2/+5
| | | | | Reformat header above separator line (added if missing) to a common format. Patch by Yoni Lavi.
* Issue #23921: Standardized documentation whitespace formatting.Serhiy Storchaka2016-05-101-1/+1
| | | | Original patch by James Edwards.
* Issue #18761: Improved cross-references in email documentation.Serhiy Storchaka2013-08-191-7/+8
|
* Fix test__locale on Mac; platform.uname() does not have a structseq-type ↵Georg Brandl2012-06-241-1/+1
| | | | interface (yet).
* Fix typo.Georg Brandl2012-06-241-1/+1
|
* #15160: Extend the new email parser to handle MIME headers.R David Murray2012-06-241-1/+70
| | | | | | | | | | | | | | | | | | | | | | | 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.
* #11785: fix the :mod: references in email package submodule titles.R David Murray2012-05-271-0/+4
| | | | Also adds the TOC entry for headerregistry.
* Make headerregistry fully part of the provisional api.R David Murray2012-05-271-0/+379
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.
generated by cgit v0.12 at 2024-12-11 14:13:21 (GMT)