email
— Email 和 MIME 处理包
»
email.parser
: 剖析 Email 消息
¶
源代码： Lib/email/parser.py
Message object structures can be created in one of two ways: they can be created from whole cloth by instantiating
Message
objects and stringing them together via
attach()
and
set_payload()
calls, or they can be created by parsing a flat text representation of the email message.
The
email
package provides a standard parser that understands most email document structures, including MIME documents. You can pass the parser a string or a file object, and the parser will return to you the root
Message
实例的对象结构。对于简单非 MIME 消息，此根对象的负载可能是包含消息文本的字符串。对于 MIME 消息，根对象会返回
True
从其
is_multipart()
method, and the subparts can be accessed via the
get_payload()
and
walk()
方法。
There are actually two parser interfaces available for use, the classic
Parser
API 和增量
FeedParser
API. The classic
Parser
API is fine if you have the entire text of the message in memory as a string, or if the entire message lives in a file on the file system.
FeedParser
is more appropriate for when you’re reading the message from a stream which might block waiting for more input (e.g. reading an email message from a socket). The
FeedParser
can consume and parse the message incrementally, and only returns the root object when you close the parser
[1]
.
Note that the parser can be extended in limited ways, and of course you can implement your own parser completely from scratch. There is no magical connection between the
email
包的捆绑剖析器和
Message
class, so your custom parser can create message object trees any way it finds necessary.
The
FeedParser
，导入从
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 (e.g. a socket). The
FeedParser
can of course be used to parse an email message fully contained in a string or a file, but the classic
Parser
API may be more convenient for such use cases. The semantics and results of the two parser APIs are identical.
The
FeedParser
‘s API is simple; you create an instance, feed it a bunch of text until there’s no more to feed it, then close the parser to retrieve the root message object. The
FeedParser
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
FeedParser
:
email.parser.
FeedParser
(
_factory=email.message.Message
,
*
,
policy=policy.compat32
)
¶
创建
FeedParser
实例。可选
_factory
is a no-argument callable that will be called whenever a new message object is needed. It defaults to the
email.message.Message
类。
若
policy
有指定 (它必须是实例化的
policy
class) use the rules it specifies to update the representation of the message. If
policy
未设置，使用
compat32
策略，保持向后兼容 Python 3.2 版 email 包。更多信息见
policy
文档编制。
3.3 版改变： 添加 policy 关键词。
feed
(
data
)
¶
Feed the
FeedParser
some more data.
data
should be a string containing one or more lines. The lines can be partial and the
FeedParser
will stitch such partial lines together properly. The lines in the string can have any of the common three line endings, carriage return, newline, or carriage return and newline (they can even be mixed).
close
(
)
¶
Closing a
FeedParser
completes the parsing of all previously fed data, and returns the root message object. It is undefined what happens if you feed more data to a closed
FeedParser
.
email.parser.
BytesFeedParser
(
_factory=email.message.Message
)
¶
Works exactly like
FeedParser
except that the input to the
feed()
method must be bytes and not string.
3.2 版新增。
The
Parser
类，导入自
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 string or file. The
email.parser
module also provides header-only parsers, called
HeaderParser
and
BytesHeaderParser
, which can be used if you’re only interested in the headers of the message.
HeaderParser
and
BytesHeaderParser
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 as a string. They have the same API as the
Parser
and
BytesParser
类。
3.3 版新增： The BytesHeaderParser class.
email.parser.
Parser
(
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
The constructor for the
Parser
class takes an optional argument
_class
. This must be a callable factory (such as a function or a class), and it is used whenever a sub-message object needs to be created. It defaults to
Message
(见
email.message
). The factory will be called without arguments.
若
policy
有指定 (它必须是实例化的
policy
class) use the rules it specifies to update the representation of the message. If
policy
未设置，使用
compat32
策略，保持向后兼容 Python 3.2 版 email 包。更多信息见
policy
文档编制。
3.3 版改变： 移除 strict argument that was deprecated in 2.4. Added the policy 关键词。
The other public
Parser
methods are:
parse
(
fp
,
headersonly=False
)
¶
Read all the data from the 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.
The text contained in fp must be formatted as a block of RFC 2822 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).
可选
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.
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 exactly equivalent to wrapping
text
在
StringIO
instance first and calling
parse()
.
可选
headersonly
is as with the
parse()
方法。
email.parser.
BytesParser
(
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
This class is exactly parallel to
Parser
, but handles bytes input. The
_class
and
strict
arguments are interpreted in the same way as for the
Parser
构造函数。
若
policy
有指定 (它必须是实例化的
policy
class) use the rules it specifies to update the representation of the message. If
policy
未设置，使用
compat32
策略，保持向后兼容 Python 3.2 版 email 包。更多信息见
policy
文档编制。
3.3 版改变： 移除 strict 自变量。添加 policy 关键词。
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()
methods on file-like objects.
The bytes contained in
fp
must be formatted as a block of
RFC 2822
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
(
text
,
headersonly=False
)
¶
类似于
parse()
方法，除了它接受
像字节对象
instead of a file-like object. Calling this method is equivalent to wrapping
text
在
BytesIO
instance first and calling
parse()
.
可选
headersonly
is as with the
parse()
方法。
3.2 版新增。
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_string
(
s
,
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
Return a message object structure from a string. This is exactly equivalent to
Parser().parsestr(s)
.
_class
and
policy
的解释就像
Parser
类构造函数。
3.3 版改变： 移除 strict 自变量。添加 policy 关键词。
email.
message_from_bytes
(
s
,
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
返回消息对象结构从
像字节对象
. This is exactly equivalent to
BytesParser().parsebytes(s)
。可选
_class
and
strict
的解释就像
Parser
类构造函数。
3.2 版新增。
3.3 版改变： 移除 strict 自变量。添加 policy 关键词。
email.
message_from_file
(
fp
,
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
返回消息对象结构树从打开
文件对象
. This is exactly equivalent to
Parser().parse(fp)
.
_class
and
policy
的解释就像
Parser
类构造函数。
3.3 版改变： 移除 strict 自变量。添加 policy 关键词。
email.
message_from_binary_file
(
fp
,
_class=email.message.Message
,
*
,
policy=policy.compat32
)
¶
返回消息对象结构树从打开二进制
文件对象
. This is exactly equivalent to
BytesParser().parse(fp)
.
_class
and
policy
的解释就像
Parser
类构造函数。
3.2 版新增。
3.3 版改变： 移除 strict 自变量。添加 policy 关键词。
Here’s an example of how you might use this at an interactive Python prompt:
>>> import email >>> msg = email.message_from_string(myString)
这里是有关剖析语义的一些注意事项：
False
for
is_multipart()
. Their
get_payload()
method will return a string object.
True
for
is_multipart()
and their
get_payload()
method will return the list of
Message
subparts.
is_multipart()
method will return
True
.
The single element in the list payload will be a sub-message object.
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
了解细节。
脚注
| [1] |
As of email package version 3.0, introduced in Python 2.4, the classic
Parser
was re-implemented in terms of the
FeedParser
, so the semantics and results are
identical between the two parsers.
|