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
I'm interested in all the nodes' data, including their attributes. When parsing this with xmltodict.parse(item_depth=2,item_callback=handle_event ...) I could not find the id attribute in the element dict. After some "debugging" I found that attribute hidden in the event tuple. Is this intended/desired behavior? I personally would prefer to have those attributes as keys in the element dict. Curious to hear any thoughts :)
The text was updated successfully, but these errors were encountered:
Thank you, indeed makes sense to prevent such a collision! And as long as the data of the attributes remains available to the user via the path tuple then it's great. Would it be an idea to point users to this in the docs?
I'm currently parsing an XML document in the format of
stream-parsing it in doc-prescribed format of
I'm interested in all the
node
s' data, including their attributes. When parsing this withxmltodict.parse(item_depth=2,item_callback=handle_event ...)
I could not find theid
attribute in theelement
dict. After some "debugging" I found that attribute hidden in theevent
tuple. Is this intended/desired behavior? I personally would prefer to have those attributes as keys in theelement
dict. Curious to hear any thoughts :)The text was updated successfully, but these errors were encountered: