Eli Bendersky added the comment:

Thanks for the effort, Stefan, but I still think IncrementalParser is worth 
keeping. It provides functionality that doesn't currently exist in ET, and IMHO 
this functionality is both important and useful.

Renaming its methods to feed & close kills the API naming inconsistency vs. 
XMLParser and SAX's IncrementalParser. As for future directions, having it does 
not add additional constrains to those that already exist because of iterparse 
accepting a "custom" XMLParser creates compatibility problems already.

For the latter, I think I can also beef up the documentation a bit to be more 
explicit (such as requiring the XMLParser provided to iterparse to derive from 
ET.XMLParser; otherwise, it just won't have the required _setevents).

----------

_______________________________________
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

Reply via email to