email.policy ：策略对象
email.policy
email
email.errors
源代码： Lib/email/errors.py
下列异常类的定义在 email.errors 模块：
这是所有异常的基类 email 包可以引发。派生自标准 Exception 类且没有定义额外方法。
Exception
这异常基类引发通过 Parser 类。派生自 MessageError 。此类还被剖析器内部使用通过 headerregistry .
Parser
MessageError
headerregistry
Raised under some error conditions when parsing the RFC 5322 headers of a message, this class is derived from MessageParseError 。 set_boundary() method will raise this error if the content type is unknown when the method is called. Header may raise this error for certain base64 decoding errors, and when an attempt is made to create a header that appears to contain an embedded header (that is, there is what is supposed to be a continuation line that has no leading whitespace and looks like a header).
MessageParseError
set_boundary()
Header
弃用且不再使用。
被引发当将负载添加到 Message 对象使用 add_payload() , but the payload is already a scalar and the message’s Content-Type main type is not either multipart or missing. MultipartConversionError multiply inherits from MessageError 和内置 TypeError .
Message
add_payload()
MultipartConversionError
TypeError
由于 Message.add_payload() is deprecated, this exception is rarely raised in practice. However the exception may also be raised if the attach() method is called on an instance of a class derived from MIMENonMultipart (如 MIMEImage ).
Message.add_payload()
attach()
MIMENonMultipart
MIMEImage
This is the base class for all defects found when parsing email messages. It is derived from ValueError .
ValueError
This is the base class for all defects found when parsing email headers. It is derived from MessageDefect .
MessageDefect
Here is the list of the defects that the FeedParser can find while parsing messages. Note that the defects are added to the message where the problem was found, so for example, if a message nested inside a multipart/alternative had a malformed header, that nested message object would have a defect, but the containing messages would not.
FeedParser
所有子类化的缺陷类来自 email.errors.MessageDefect .
email.errors.MessageDefect
NoBoundaryInMultipartDefect – A message claimed to be a multipart, but had no boundary 参数。
NoBoundaryInMultipartDefect
StartBoundaryNotFoundDefect – The start boundary claimed in the Content-Type header was never found.
StartBoundaryNotFoundDefect
CloseBoundaryNotFoundDefect – A start boundary was found, but no corresponding close boundary was ever found.
CloseBoundaryNotFoundDefect
Added in version 3.3.
FirstHeaderLineIsContinuationDefect – The message had a continuation line as its first header line.
FirstHeaderLineIsContinuationDefect
MisplacedEnvelopeHeaderDefect - A “Unix From” header was found in the middle of a header block.
MisplacedEnvelopeHeaderDefect
MissingHeaderBodySeparatorDefect - A line was found while parsing headers that had no leading white space but contained no ‘:’. Parsing continues assuming that the line represents the first line of the body.
MissingHeaderBodySeparatorDefect
MalformedHeaderDefect – A header was found that was missing a colon, or was otherwise malformed.
MalformedHeaderDefect
从 3.3 版起弃用： 此缺陷尚未用于多个 Python 版本。
MultipartInvariantViolationDefect – A message claimed to be a multipart , but no subparts were found. Note that when a message has this defect, its is_multipart() method may return False even though its content type claims to be multipart .
MultipartInvariantViolationDefect
is_multipart()
False
InvalidBase64PaddingDefect – When decoding a block of base64 encoded bytes, the padding was not correct. Enough padding is added to perform the decode, but the resulting decoded bytes may be invalid.
InvalidBase64PaddingDefect
InvalidBase64CharactersDefect – When decoding a block of base64 encoded bytes, characters outside the base64 alphabet were encountered. The characters are ignored, but the resulting decoded bytes may be invalid.
InvalidBase64CharactersDefect
InvalidBase64LengthDefect – When decoding a block of base64 encoded bytes, the number of non-padding base64 characters was invalid (1 more than a multiple of 4). The encoded block was kept as-is.
InvalidBase64LengthDefect
InvalidDateDefect – When decoding an invalid or unparsable date field. The original value is kept as-is.
InvalidDateDefect
email.headerregistry : 自定义头对象
email.headerregistry
键入搜索术语或模块、类、函数名称。