[issue17902] Document that _elementtree C API cannot use custom TreeBuilder for iterparse or IncrementalParser

2013-08-26 Thread Aaron Oakley
Aaron Oakley added the comment: >From memory, the use case at the time was using a custom TreeBuilder sub-class >fed into a builtin XMLParser object. The code would construct a builder >separately and keep a reference to it around. The builder would delegate calls >to start(),

[issue17902] Document that _elementtree C API cannot use custom TreeBuilder for iterparse or IncrementalParser

2013-06-17 Thread Aaron Oakley
Aaron Oakley added the comment: So sorry, I just found the emails from the bug tracker in my spam folder. Anyhow, I've now signed the CLA. -- ___ Python tracker <http://bugs.python.org/is

[issue17902] Document that _elementtree C API cannot use custom TreeBuilder for iterparse or IncrementalParser

2013-05-03 Thread Aaron Oakley
New submission from Aaron Oakley: It would really help to document that the C API can only use the default xml.etree.ElementTree.TreeBuilder for targets with iterparse (and by extension, IncrementalParser). I got a nice surprise about that when I went from 3.2 to 3.3 and started getting

[issue17901] _elementtree.TreeBuilder raises IndexError on end if constructed with element_factory=None

2013-05-03 Thread Aaron Oakley
New submission from Aaron Oakley: When the _elementtree module is in use, the TreeBuilder class will raise an IndexError in treebuilder_handle_end if __init__ was passed "None". I discovered this while writing a subclass of TreeBuilder with a modified __init__ method that de