Searched refs:FeedParser (Results 1 – 9 of 9) sorted by relevance
25 :class:`Parser` API and the incremental :class:`FeedParser` API. The classic28 :class:`FeedParser` is more appropriate for when you're reading the message from30 from a socket). The :class:`FeedParser` can consume and parse the message40 FeedParser API45 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 used53 The :class:`FeedParser`'s API is simple; you create an instance, feed it a bunch55 root message object. The :class:`FeedParser` is extremely accurate when parsing62 Here is the API for the :class:`FeedParser`:65 .. class:: FeedParser([_factory])[all …]
64 Here's the list of the defects that the :class:`~email.parser.FeedParser`
132 * The :class:`~email.parser.FeedParser` class was introduced, and the134 :class:`~email.parser.FeedParser`. All parsing therefore is
12 from email.feedparser import FeedParser64 feedparser = FeedParser(self._class)
158 class FeedParser: class
2634 from email.feedparser import FeedParser2635 feedparser = FeedParser()
1071 available in the :mod:`email.FeedParser` module. The new parser doesn't require
1710 - Issue #21448: Changed FeedParser feed() to avoid O(N**2) behavior when
2359 + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be