bpo-43292: Fix file leak in ET.iterparse() when not exhausted #31696
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
bpo-43292: This fixes the file leak in
xml.etree.ElementTree.iterparsewhen the iterator is garbage collected before being exhausted.Regression test fails on main.
Related, but not done in this PR: bpo-25707 is a request for an explicit
close()method foriterparse(). I am not certain if that feature would still be desired after this change.https://bugs.python.org/issue43292