traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge #11216: document all possible set_charset execution paths.

This commit is contained in:
R David Murray 2011-03-15 17:43:21 -04:00
parent b637680f7e 729c5e203d
commit 31f218bc6b
1 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
Doc/library/email.message.rst
View File

@ -139,15 +139,22 @@ Here are the methods of the :class:`Message` class:
string naming a character set, or ``None``. If it is a string, it will string naming a character set, or ``None``. If it is a string, it will
be converted to a :class:`~email.charset.Charset` instance. If *charset* be converted to a :class:`~email.charset.Charset` instance. If *charset*
is ``None``, the ``charset`` parameter will be removed from the is ``None``, the ``charset`` parameter will be removed from the
:mailheader:`Content-Type` header. Anything else will generate a :mailheader:`Content-Type` header (the message will not be otherwise
:exc:`TypeError`. modified). Anything else will generate a :exc:`TypeError`.
The message will be assumed to be of type :mimetype:`text/\*` encoded with If there is no existing :mailheader:`MIME-Version` header one will be
*charset.input_charset*. It will be converted to *charset.output_charset* added. If there is no existing :mailheader:`Content-Type` header, one
and encoded properly, if needed, when generating the plain text will be added with a value of :mimetype:`text/plain`. Whether the
representation of the message. MIME headers (:mailheader:`MIME-Version`, :mailheader:`Content-Type` header already exists or not, its ``charset``
:mailheader:`Content-Type`, :mailheader:`Content-Transfer-Encoding`) will parameter will be set to *charset.output_charset*. If
be added as needed. *charset.input_charset* and *charset.output_charset* differ, the payload
will be re-encoded to the *output_charset*. If there is no existing
:mailheader:`Content-Transfer-Encoding` header, then the payload will be
transfer-encoded, if needed, using the specified
:class:`~email.charset.Charset`, and a header with the appropriate value
will be added. If a :mailheader:`Content-Transfer-Encoding` header
already exists, the payload is assumed to already be correctly encoded
using that :mailheader:`Content-Transfer-Encoding` and is not modified.
.. method:: get_charset() .. method:: get_charset()