diff options
author | Barry Warsaw <barry@python.org> | 2001-10-11 15:45:05 (GMT) |
---|---|---|
committer | Barry Warsaw <barry@python.org> | 2001-10-11 15:45:05 (GMT) |
commit | c7f8b86307a14deff67a79b1841e05e27b9c8360 (patch) | |
tree | f1455b77f0eb14a53fcef66a4b59bdf40150645f | |
parent | bf7a59d94b5efd1e675b8365a686b48f2b260736 (diff) | |
download | cpython-c7f8b86307a14deff67a79b1841e05e27b9c8360.zip cpython-c7f8b86307a14deff67a79b1841e05e27b9c8360.tar.gz cpython-c7f8b86307a14deff67a79b1841e05e27b9c8360.tar.bz2 |
Describe the HeaderParser class.
-rw-r--r-- | Doc/lib/emailparser.tex | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Doc/lib/emailparser.tex b/Doc/lib/emailparser.tex index 0b2cec0..724de08 100644 --- a/Doc/lib/emailparser.tex +++ b/Doc/lib/emailparser.tex @@ -24,6 +24,17 @@ no magical connection between the \module{email} package's bundled parser and the \class{Message} class, so your custom parser can create message object trees in any way it find necessary. +The primary parser class is \class{Parser} which parses both the +headers and the payload of the message. In the case of +\mimetype{multipart} messages, it will recursively parse the body of +the container message. The \module{email.Parser} module also provides +a second class, called \class{HeaderParser} which can be used if +you're only interested in the headers of the message. +\class{HeaderParser} can be much faster in this situations, since it +does not attempt to parse the message body, instead setting the +payload to the raw body as a string. \class{HeaderParser} has the +same API as the \class{Parser} class. + \subsubsection{Parser class API} \begin{classdesc}{Parser}{\optional{_class}} |