Author ncoghlan
Recipients eli.bendersky, flox, jcea, jkloth, ncoghlan, python-dev, scoder
Date 2013-08-26.07:58:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377503885.42.0.391333871251.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
Since parsers don't support changing the target after creation, I think it makes sense to deprecate passing in a parser *instance*, and instead require passing in a callback that accepts the target to use and *returns* an appropriate parser object. The "parser can only use the default TreeBuilder as a target." line in the iterparse docs is a sign that this is a more appropriate API - if iterparse needs a particular kind of target, the API should be designed so iterparse *provides* that target instead of saying "please don't use a custom target type".

However, I don't think it makes sense to provide such a callback based API until it is actually possible to implement the streaming event API using a custom target object with XMLParser.
History
Date User Action Args
2013-08-26 07:58:05ncoghlansetrecipients: + ncoghlan, jcea, scoder, jkloth, eli.bendersky, flox, python-dev
2013-08-26 07:58:05ncoghlansetmessageid: <1377503885.42.0.391333871251.issue17741@psf.upfronthosting.co.za>
2013-08-26 07:58:05ncoghlanlinkissue17741 messages
2013-08-26 07:58:05ncoghlancreate