email.errors ：异常和缺陷类

源代码： Lib/email/errors.py

下列异常类的定义在 email.errors 模块：

exception email.errors. MessageError

这是所有异常的基类 email 包可以引发。派生自标准 Exception 类且没有定义额外方法。

exception email.errors. MessageParseError

这异常基类引发通过 Parser 类。派生自 MessageError 。此类还被剖析器内部使用通过 headerregistry .

exception email.errors. HeaderParseError

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).

exception email.errors. BoundaryError

弃用且不再使用。

exception email.errors. MultipartConversionError

被引发当将负载添加到 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() 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 ).

exception email.errors. HeaderWriteError

Raised when an error occurs when the generator outputs headers.

exception email.errors. MessageDefect

This is the base class for all defects found when parsing email messages. It is derived from ValueError .

exception email.errors. HeaderDefect

This is the base class for all defects found when parsing email headers. It is derived from 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.

所有子类化的缺陷类来自 email.errors.MessageDefect .

  • NoBoundaryInMultipartDefect – A message claimed to be a multipart, but had no boundary 参数。

  • StartBoundaryNotFoundDefect – The start boundary claimed in the Content-Type header was never found.

  • CloseBoundaryNotFoundDefect – A start boundary was found, but no corresponding close boundary was ever found.

    Added in version 3.3.