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 scoder
Recipients eli.bendersky, flox, jcea, pitrou, python-dev, scoder
Date 2013-08-09.15:30:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376062235.29.0.365491025686.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
> 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 self.target.start(), thus calling into the TreeBuilder. That's the thing that constructs the elements that the IncrementalParser collects in its events list.
History
Date User Action Args
2013-08-09 15:30:35scodersetrecipients: + scoder, jcea, pitrou, eli.bendersky, flox, python-dev
2013-08-09 15:30:35scodersetmessageid: <1376062235.29.0.365491025686.issue17741@psf.upfronthosting.co.za>
2013-08-09 15:30:35scoderlinkissue17741 messages
2013-08-09 15:30:35scodercreate