This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author scoder
Recipients eli.bendersky, padremayi, scoder
Date 2022-02-23.11:49:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645616965.57.0.447820375852.issue46798@roundup.psfhosted.org>
In-reply-to
Content
> IMHO if the developer doesn't manage the XML itself it is VERY unreasonable to use the document value and not the developer one.

I disagree. If the document says "this is the default if no explicit value if given", then I consider that just as good as providing a value each time. Meaning, the attribute *is* in fact present, just not explicitly spelled out on the element.

I would specifically like to avoid adding a new option just to override the way the document distributes its attribute value spelling across DTD and document structure. In particular, the .get() method is the wrong place to deal with this.

You can probably configure the parser to ignore the internal DTD subset, if that's what you want.
History
Date User Action Args
2022-02-23 11:49:25scodersetrecipients: + scoder, eli.bendersky, padremayi
2022-02-23 11:49:25scodersetmessageid: <1645616965.57.0.447820375852.issue46798@roundup.psfhosted.org>
2022-02-23 11:49:25scoderlinkissue46798 messages
2022-02-23 11:49:25scodercreate