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
bpo-7214: TreeBuilder.end(tag) differs between cElementTree and ElementTree
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2009-10-26.23:33:36.824>created_at=<Date2009-10-26.23:32:31.813>labels= ['type-bug', 'library']
title='TreeBuilder.end(tag) differs between cElementTree and ElementTree'updated_at=<Date2009-10-27.01:40:40.104>user='https://bugs.python.org/merrellb'
In the pure python ElementTree, the tag passed to the end() tag is
verified to be closing the last tag opened (self._last).
This cElementTree performs no such validation and closes the last tag
regardless of what tag is passed to the method.
In my mind this raises a couple questions beyond simply fixing this
discrepancy.
Why make this tag mandatory if it has no effect in the cElementTree
version (and in the pure python version is only used to verify the user
isn't confused what tag they are closing)
Could the argument be removed, simply closing the last tag if not
present?
Or could the behavior be changed to actually influence which tag is
closed, allowing one to close all tags out to a specific
outer/encompassing tag (much like close(), closes all tags)?
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: