[issue14168] minidom behaves differently in 3.3 compared to 3.2

Vinay Sajip added the comment: Upon inspection, _ensure_attributes() is only called in _get_attributes(), setAttributeNode() and _set_attribute_node(). The last of these is only called by setAttributeNode(), and it would appear that setAttributeNode() is only called if there *are* attributes.

[issue14168] minidom behaves differently in 3.3 compared to 3.2

Vinay Sajip added the comment: The error which prompted this issue was not caused by external code peeking into the internals - it was just my toy test script which did that. The error came up in Django testing: == ERROR: tes

[issue14168] minidom behaves differently in 3.3 compared to 3.2

Éric Araujo added the comment: That would be caused by Martin’s change in 5d27a32ebbcc. I don’t see the docs marking _attrs public, so I think this is not a bug. -- nosy: +eric.araujo ___ Python tracker

[issue14168] minidom behaves differently in 3.3 compared to 3.2

New submission from Vinay Sajip : The following script, minidom_test.py, from xml.dom import minidom data = b''' http://www.w3.org/2005/Atom"; version="2.0"> https://example.com/blog/ https://example.com/rss2/"; rel="self"> https://example.com/blog/1/ ''' doc = mi