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.15:53:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> > Unless I'm reading it wrong, when _setevents() is called, the
> > internal
> > hooks are rewired to populate the events list, rather than call the
> > corresponding TreeBuilder methods. So, yes, there's a TreeBuilder
> > somewhere, but it stands unused.
> Yes, you *are* reading it wrong. For example, the "start" callback
> calls self._start_list, which in turn calls,
> thus calling into the TreeBuilder. That's the thing that constructs
> the elements that the IncrementalParser collects in its events list.

Ah, indeed, my bad. That said, using a custom TreeBuilder-alike
would necessitate changes in the C implementation of XMLParser.
(which, I suppose, is why the _setevents hack exists in the first
Date User Action Args
2013-08-09 15:53:23pitrousetrecipients: + pitrou, jcea, scoder, eli.bendersky, flox, python-dev
2013-08-09 15:53:23pitroulinkissue17741 messages
2013-08-09 15:53:22pitroucreate