email.parser : 剖析 Email 消息 ¶

FeedParser API ¶

BytesFeedParser ，导入从 email.feedparser module, provides an API that is conducive to incremental parsing of email messages, such as would be necessary when reading the text of an email message from a source that can block (such as a socket). The BytesFeedParser can of course be used to parse an email message fully contained in a 像字节对象 , string, or file, but the BytesParser API may be more convenient for such use cases. The semantics and results of the two parser APIs are identical.

BytesFeedParser ’s API is simple; you create an instance, feed it a bunch of bytes until there’s no more to feed it, then close the parser to retrieve the root message object. The BytesFeedParser is extremely accurate when parsing standards-compliant messages, and it does a very good job of parsing non-compliant messages, providing information about how a message was deemed broken. It will populate a message object’s defects attribute with a list of any problems it found in a message. See the email.errors module for the list of defects that it can find.

Here is the API for the BytesFeedParser :

class email.parser. BytesFeedParser ( _factory=None , * , policy=policy.compat32 ) ¶

创建 BytesFeedParser 实例。可选 _factory is a no-argument callable; if not specified use the message_factory 从 policy 。调用 _factory whenever a new message object is needed.

若 policy is specified use the rules it specifies to update the representation of the message. If policy 未设置，使用 compat32 policy, which maintains backward compatibility with the Python 3.2 version of the email package and provides Message as the default factory. All other policies provide EmailMessage as the default _factory . For more information on what else policy controls, see the policy 文档编制。

注意： 应始终指定 policy 关键字 ；默认将更改为 email.policy.default 在未来 Python 版本中。

3.2 版新增。

3.3 版改变： 添加 policy 关键词。

3.6 版改变： _factory 默认为策略 message_factory .

feed ( data ) ¶

向剖析器馈送一些更多数据。 data 应该为 像字节对象 containing one or more lines. The lines can be partial and the parser will stitch such partial lines together properly. The lines can have any of the three common line endings: carriage return, newline, or carriage return and newline (they can even be mixed).

close ( ) ¶

Complete the parsing of all previously fed data and return the root message object. It is undefined what happens if feed() is called after this method has been called.

class email.parser. FeedParser ( _factory=None , * , policy=policy.compat32 ) ¶

工作像 BytesFeedParser except that the input to the feed() method must be a string. This is of limited utility, since the only way for such a message to be valid is for it to contain only ASCII text or, if utf8 is True , no binary attachments.

3.3 版改变： 添加 policy 关键词。

剖析器 API ¶

BytesParser 类，导入自 email.parser module, provides an API that can be used to parse a message when the complete contents of the message are available in a 像字节对象 or file. The email.parser 模块还提供 Parser for parsing strings, and header-only parsers, BytesHeaderParser and HeaderParser , which can be used if you’re only interested in the headers of the message. BytesHeaderParser and HeaderParser can be much faster in these situations, since they do not attempt to parse the message body, instead setting the payload to the raw body.

class email.parser. BytesParser ( _class=None , * , policy=policy.compat32 ) ¶

创建 BytesParser instance. The _class and policy arguments have the same meaning and semantics as the _factory and policy arguments of BytesFeedParser .

注意： 应始终指定 policy 关键字 ；默认将更改为 email.policy.default 在未来 Python 版本中。

3.3 版改变： 移除 strict argument that was deprecated in 2.4. Added the policy 关键词。

3.6 版改变： _class 默认为策略 message_factory .

parse ( fp , headersonly=False ) ¶

Read all the data from the binary file-like object fp , parse the resulting bytes, and return the message object. fp must support both the readline() 和 read() 方法。

The bytes contained in fp must be formatted as a block of RFC 5322 (或者，若 utf8 is True , RFC 6532 ) style headers and header continuation lines, optionally preceded by an envelope header. The header block is terminated either by the end of the data or by a blank line. Following the header block is the body of the message (which may contain MIME-encoded subparts, including subparts with a Content-Transfer-Encoding of 8bit ).

可选 headersonly is a flag specifying whether to stop parsing after reading the headers or not. The default is False , meaning it parses the entire contents of the file.

parsebytes ( bytes , headersonly=False ) ¶

类似 parse() 方法，除了它接受 像字节对象 而不是像文件对象。调用此方法在 像字节对象 is equivalent to wrapping bytes 在 BytesIO instance first and calling parse() .

可选 headersonly is as with the parse() 方法。

3.2 版新增。

class email.parser. BytesHeaderParser ( _class=None , * , policy=policy.compat32 ) ¶

准确像 BytesParser ，除了 headersonly 默认为 True .

3.3 版新增。

class email.parser. Parser ( _class=None , * , policy=policy.compat32 ) ¶

此类平行于 BytesParser ，但处理字符串输入。

3.3 版改变： 移除 strict 自变量。添加 policy 关键词。

3.6 版改变： _class 默认为策略 message_factory .

parse ( fp , headersonly=False ) ¶

Read all the data from the text-mode file-like object fp , parse the resulting text, and return the root message object. fp must support both the readline() 和 read() methods on file-like objects.

Other than the text mode requirement, this method operates like BytesParser.parse() .

parsestr ( text , headersonly=False ) ¶

类似 parse() method, except it takes a string object instead of a file-like object. Calling this method on a string is equivalent to wrapping text 在 StringIO instance first and calling parse() .

可选 headersonly is as with the parse() 方法。

class email.parser. HeaderParser ( _class=None , * , policy=policy.compat32 ) ¶

准确像 Parser ，除了 headersonly 默认为 True .

Since creating a message object structure from a string or a file object is such a common task, four functions are provided as a convenience. They are available in the top-level email package namespace.

email. message_from_bytes ( s , _class=None , * , policy=policy.compat32 ) ¶

返回消息对象结构从 像字节对象 。这相当于 BytesParser().parsebytes(s) 。可选 _class and policy 的解释采用 BytesParser 类构造函数。

3.2 版新增。

3.3 版改变： 移除 strict 自变量。添加 policy 关键词。

email. message_from_binary_file ( fp , _class=None , * , policy=policy.compat32 ) ¶

返回消息对象结构树从打开二进制 文件对象 。这相当于 BytesParser().parse(fp) . _class and policy 的解释采用 BytesParser 类构造函数。

3.2 版新增。

3.3 版改变： 移除 strict 自变量。添加 policy 关键词。

email. message_from_string ( s , _class=None , * , policy=policy.compat32 ) ¶

从字符串返回消息对象结构。这相当于 Parser().parsestr(s) . _class and policy 的解释采用 Parser 类构造函数。

3.3 版改变： 移除 strict 自变量。添加 policy 关键词。

email. message_from_file ( fp , _class=None , * , policy=policy.compat32 ) ¶

返回消息对象结构树从打开 文件对象 。这相当于 Parser().parse(fp) . _class and policy 的解释采用 Parser 类构造函数。

3.3 版改变： 移除 strict 自变量。添加 policy 关键词。

3.6 版改变： _class 默认为策略 message_factory .

Here’s an example of how you might use message_from_bytes() at an interactive Python prompt:

>>> import email
>>> msg = email.message_from_bytes(myBytes)
								

其它注意事项 ¶

这里是有关剖析语义的一些注意事项：

• 大多数非 multipart type messages are parsed as a single message object with a string payload. These objects will return False for is_multipart() ，和 iter_parts() will yield an empty list.

• 所有 multipart type messages will be parsed as a container message object with a list of sub-message objects for their payload. The outer container message will return True for is_multipart() ，和 iter_parts() will yield a list of subparts.

• Most messages with a content type of message/* (譬如 message/delivery-status and message/rfc822 ) will also be parsed as container object containing a list payload of length 1. Their is_multipart() method will return True . The single element yielded by iter_parts() will be a sub-message object.

• Some non-standards-compliant messages may not be internally consistent about their multipart -edness. Such messages may have a Content-Type header of type multipart , but their is_multipart() method may return False . If such messages were parsed with the FeedParser , they will have an instance of the MultipartInvariantViolationDefect class in their defects attribute list. See email.errors 了解细节。