From 48330687f36bb452e17480e78bf3ca17f9728e87 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Mon, 30 Sep 2002 23:07:35 +0000 Subject: [PATCH] Docstring consistency with the updated .tex files. --- Lib/email/Header.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Lib/email/Header.py b/Lib/email/Header.py index 0f2eb32ea8..a40226dc14 100644 --- a/Lib/email/Header.py +++ b/Lib/email/Header.py @@ -205,11 +205,12 @@ class Header: s may be a byte string or a Unicode string. If it is a byte string (i.e. isinstance(s, StringType) is true), then charset is the encoding of that byte string, and a UnicodeError will be raised if the string - cannot be decoded with that charset. If `s' is a Unicode string, then + cannot be decoded with that charset. If s is a Unicode string, then charset is a hint specifying the character set of the characters in the string. In this case, when producing an RFC 2822 compliant header using RFC 2047 rules, the Unicode string will be encoded using the - following charsets in order: us-ascii, the charset hint, utf-8. + following charsets in order: us-ascii, the charset hint, utf-8. The + first character set not to provoke a UnicodeError is used. """ if charset is None: charset = self._charset @@ -376,7 +377,7 @@ class Header: return joiner.join(chunks) def encode(self): - """Encode a message header, possibly converting charset and encoding. + """Encode a message header into an RFC-compliant format. There are many issues involved in converting a given string for use in an email header. Only certain character sets are readable in most -- 2.49.0