Author fdrake
Recipients fdrake, ygale
Date 2008-03-28.18:42:39
SpamBayes Score 0.0104896
Marked as misclassified No
Message-id <1206729761.44.0.790843410568.issue2174@psf.upfronthosting.co.za>
In-reply-to
Content
It's certainly arguable that the current behavior is a bug, though I
suspect it shouldn't be considered major since I've not seen any prior
complaints about this.

It should be easy to fix the bug you describe by taking the character
stream and encoding it before feeding it to the XML parser; Expat can
certainly be forced to take a known encoding, ignoring what's in the XML
declaration.

On the other hand, it's not at all clear that changing this is
worthwhile.  This API borrows quite literally from the Java SAX APIs;
perhaps this separation of the character stream from the byte stream
makes sense for some of the Java XML parsers, but I don't know that
there are any Python parsers that benefit from that separation.
History
Date User Action Args
2008-03-28 18:42:41fdrakesetspambayes_score: 0.0104896 -> 0.0104896
recipients: + fdrake, ygale
2008-03-28 18:42:41fdrakesetspambayes_score: 0.0104896 -> 0.0104896
messageid: <1206729761.44.0.790843410568.issue2174@psf.upfronthosting.co.za>
2008-03-28 18:42:40fdrakelinkissue2174 messages
2008-03-28 18:42:39fdrakecreate