Lines Matching refs:FeedParser

25 :class:`Parser` API and the incremental :class:`FeedParser` API.  The classic
28 :class:`FeedParser` is more appropriate for when you're reading the message from
30 from a socket).  The :class:`FeedParser` can consume and parse the message
40 FeedParser API
45 The :class:`FeedParser`, imported from the :mod:`email.feedparser` module,
48 that can block (e.g. a socket).  The :class:`FeedParser` can of course be used
53 The :class:`FeedParser`'s API is simple; you create an instance, feed it a bunch
55 root message object.  The :class:`FeedParser` is extremely accurate when parsing
62 Here is the API for the :class:`FeedParser`:
65 .. class:: FeedParser([_factory])
67    Create a :class:`FeedParser` instance.  Optional *_factory* is a no-argument
74       Feed the :class:`FeedParser` some more data.  *data* should be a string
76       :class:`FeedParser` will stitch such partial lines together properly.  The
84       Closing a :class:`FeedParser` completes the parsing of all previously fed
86       if you feed more data to a closed :class:`FeedParser`.
115       around the new-in-Python 2.4 :class:`FeedParser`, *all* parsing is
219   If such messages were parsed with the :class:`~email.parser.FeedParser`,
228    :class:`~email.parser.FeedParser`, so the semantics and results are