This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients eli.bendersky, flox, jcea, pitrou, python-dev, scoder
Date 2013-08-09.14:28:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> > The point is not to build a tree of potentially unbounded size
> > (think
> > XMPP). The point is to yield events in a non-blocking way
> > (iterparse()
> > is blocking, which makes it useless for non-blocking applications).
> Ok, but that's the only difference. Instead of getting the events
> from the parser, you could equally well get them from the
> TreeBuilder, also in a non-blocking way.

But your TreeBuilder is also growing a tree internally, and therefore
eating more and more memory, right?

I don't see the point of stuffing different kinds of functionality
inside a single class. It makes the intended use less obvious, and
errors more likely. Right now, IncrementalParser has a simple API,
and there's a single way to use it.
Date User Action Args
2013-08-09 14:28:22pitrousetrecipients: + pitrou, jcea, scoder, eli.bendersky, flox, python-dev
2013-08-09 14:28:22pitroulinkissue17741 messages
2013-08-09 14:28:22pitroucreate