[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Change by Zackery Spytz : -- versions: +Python 3.10 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Change by Zackery Spytz : -- nosy: +ZackerySpytz nosy_count: 3.0 -> 4.0 pull_requests: +21929 pull_request: https://github.com/python/cpython/pull/23012 ___ Python tracker ___

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Change by Jonathan Gossage : -- keywords: +patch pull_requests: +9272 stage: -> patch review ___ Python tracker ___ ___

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Tal Einat added the comment: Proposing removal of SAX2DOM doesn't seem unreasonable to me. However, considering it hasn't been removed so far, we'll need good reason to do so since that would break backwards compatibility. Jonathan, if the solution to this is simple, I say go for it and

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Jonathan Gossage added the comment: This test case demonstrates that the issue still exists in 3.8. The fix is relatively simple but I am unsure whether it is worthwhile as the original comments on the quality and usability of SAX2DOM are spot on. My recommendation would be to mark it as

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

New submission from Mark Smith mark.sm...@practicalpoetry.co.uk: pulldom.SAX2DOM raises a TypeError if it encounters a processing instruction before the root element of an XML document. It is valid to have a processing instruction before the root node of a document (and SAX2DOM's superclass,

[issue9453] pulldom.SAX2DOM Doesn't support processing instructions before the root element

Mark Smith mark.sm...@practicalpoetry.co.uk added the comment: My recommendation is that SAX2DOM is deprecated and removed from the standard library rather than fixing this issue. The class is currently undocumented, has weird behaviour, and is unused within the Python standard library, so I