diff options
author | Ezio Melotti <ezio.melotti@gmail.com> | 2023-10-11 20:24:12 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-10-11 20:24:12 (GMT) |
commit | bb7923f556537a463c403dc1097726d8a8e1a6f2 (patch) | |
tree | 8efe3bdbcad4b383d2c584ecbd5d1dc0fdaa4c9c /Doc/library/email.policy.rst | |
parent | c523ce0f434582580a3721e15cb7dd6b56ad0236 (diff) | |
download | cpython-bb7923f556537a463c403dc1097726d8a8e1a6f2.zip cpython-bb7923f556537a463c403dc1097726d8a8e1a6f2.tar.gz cpython-bb7923f556537a463c403dc1097726d8a8e1a6f2.tar.bz2 |
gh-110631: Fix reST indentation in `Doc/library` (#110685)
Fix wrong indentation in the Doc/library dir.
Diffstat (limited to 'Doc/library/email.policy.rst')
-rw-r--r-- | Doc/library/email.policy.rst | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/Doc/library/email.policy.rst b/Doc/library/email.policy.rst index 2439dee..fd47dd0 100644 --- a/Doc/library/email.policy.rst +++ b/Doc/library/email.policy.rst @@ -557,17 +557,17 @@ more closely to the RFCs relevant to their domains. With all of these :class:`EmailPolicies <.EmailPolicy>`, the effective API of the email package is changed from the Python 3.2 API in the following ways: - * Setting a header on a :class:`~email.message.Message` results in that - header being parsed and a header object created. +* Setting a header on a :class:`~email.message.Message` results in that + header being parsed and a header object created. - * Fetching a header value from a :class:`~email.message.Message` results - in that header being parsed and a header object created and - returned. +* Fetching a header value from a :class:`~email.message.Message` results + in that header being parsed and a header object created and + returned. - * Any header object, or any header that is refolded due to the - policy settings, is folded using an algorithm that fully implements the - RFC folding algorithms, including knowing where encoded words are required - and allowed. +* Any header object, or any header that is refolded due to the + policy settings, is folded using an algorithm that fully implements the + RFC folding algorithms, including knowing where encoded words are required + and allowed. From the application view, this means that any header obtained through the :class:`~email.message.EmailMessage` is a header object with extra |