Nick Coghlan added the comment: The whole point of the new API is not to replace XMLParser, but to provide a convenience API to set up a particular combination of an XMLParser with a particular kind of custom target. It just happens that actually *implementing it* that way doesn't work right with the current code. It is *not* necessary (or even appropriate) for it to serve as a new building block, but as a convenience API to compose *existing* building blocks in a particular way (or should be, except that composition doesn't currently work right).
Once the underlying deficiencies are fixed, then the event capturing target can be exposed directly, but in the meantime, the *composed* version can be exposed by relying on internal APIs. We could call the new class XMLParserWithEventCapturingTarget, but that's a little clumsy :) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17741> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
