You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fix unintended behavior change in elementtree introduced in #114269 #114737
As it was discussed here, after merging of #114269it.root is no longer None once an iterator is created. There was no intention to change this, it should be reverted.
Meanwhile, I think it will be good to add test for root attribute.
Right after function returned iterator: it.root must be None.
After iterator exhaustion: it.root must be an instance of xml.etree.ElementTree.Element.
changed the title [-]Fix unintended behavior change introduced in #114269[/-][+]Fix unintended behavior change in elementtree introduced in #114269[/+]on Jan 30, 2024
Activity
[-]Fix unintended behavior change introduced in #114269[/-][+]Fix unintended behavior change in elementtree introduced in #114269[/+]pythongh-114737: Revert change to ElementTree.iterparse "root" attribute
gh-114737: Revert change to ElementTree.iterparse "root" attribute (G…
pythongh-114737: Revert change to ElementTree.iterparse "root" attrib…
pythongh-114737: Revert change to ElementTree.iterparse "root" attrib…
serhiy-storchaka commentedon Jan 31, 2024
Thank you for your report @Prometheus3375.
[3.12] gh-114737: Revert change to ElementTree.iterparse "root" attri…
[3.11] gh-114737: Revert change to ElementTree.iterparse "root" attri…
pythongh-114737: Revert change to ElementTree.iterparse "root" attrib…