[issue14762] ElementTree memory leak

2012-05-09 Thread Giuseppe Attardi
Changes by Giuseppe Attardi : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue14762] ElementTree memory leak

2012-05-09 Thread Giuseppe Attardi
Giuseppe Attardi added the comment: You are right, I should discard the elements. Thank you. -- ___ Python tracker ___ ___ Python-bu

[issue14762] ElementTree memory leak

2012-05-09 Thread Jesús Cea Avión
Jesús Cea Avión added the comment: Can this be reproduced in 3.2/3.3? -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mail

[issue14762] ElementTree memory leak

2012-05-09 Thread Eli Bendersky
Eli Bendersky added the comment: Can you specify how you import ET? I.e. from the pure Python or the C accelerator? Also, do you realize that the element iterparse returns should be discarded with 'clear'? [see tutorial here: http://eli.thegreenplace.net/2012/03/15/processing-xml-in-python-w

[issue14762] ElementTree memory leak

2012-05-09 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +eli.bendersky, flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue14762] ElementTree memory leak

2012-05-09 Thread Giuseppe Attardi
New submission from Giuseppe Attardi : I confirm the presence of a serious memory leak in ElementTree, using the iterparse() function. Memory grows disproportionately to dozens of GB when parsing a large XML file. For further information, see discussion in: http://www.gossamer-threads.com/li