[issue10026] xml.dom.pulldom strange behavior

Myrosia Dzikovska added the comment: I have the same problem, and I tried the solution suggested in here, namely expanding the node at END_ELEMENT. It does not work, raising the following exception: Traceback (most recent call last): File "/group/project/onrbee/data/beetle2-eval-09/annotat

[issue10026] xml.dom.pulldom strange behavior

Changes by Georg Brandl : -- resolution: -> works for me status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue10026] xml.dom.pulldom strange behavior

Amaury Forgeot d'Arc added the comment: Yes, sax parsers may split CHARACTER events. See also the discussion: http://www.mail-archive.com/xml-...@python.org/msg00234.html Again, the END_ELEMENT event is guaranteed to return the complete node. -- ___

[issue10026] xml.dom.pulldom strange behavior

Vojtěch Rylko added the comment: Program below also splits two of 10 000 elements into two rows. Is it acceptable behavior? OUTPUT (ill part) = PROGRAM = for event, node in events: if event == pulldom.CHARACTERS: print node.data --

[issue10026] xml.dom.pulldom strange behavior

Amaury Forgeot d'Arc added the comment: Please read http://docs.python.org/library/xml.etree.elementtree.html?highlight=elementtree#xml.etree.ElementTree.iterparse At START_ELEMENT, the element is not guaranteed to be fully populated; you should handle the END_ELEMENT event instead. This should

[issue10026] xml.dom.pulldom strange behavior

New submission from Vojtěch Rylko : Hi, I have file with 10 000 records of same element item (always same): $ head test.xml Twitter Twitter Twitter Twitter Twitter Twitter Twitter Twitter Twitter And run simply program for printing content of element section: $ python pulldom.py test.xml | h