[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- components: +XML ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174 ___

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Fred L. Drake, Jr. added the comment: Given that this has languished this long, patching historical releases seems pointless. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- components: +Library (Lib) -Documentation, XML resolution: - fixed stage: - resolved versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2 ___ Python tracker

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Serhiy Storchaka added the comment: Fixed in issue2175 (in 3.5 only). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174 ___ ___

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Serhiy Storchaka added the comment: Issue2175 has a patch that covers all three issues: issue1483, issue2174 and issue2175. I hesitate what parts of the patch are worth to be applied to maintained releases. -- nosy: +serhiy.storchaka ___ Python

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +Expat parser parses strings only when XML encoding is UTF-8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174 ___

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174 ___

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Fred L. Drake, Jr. [EMAIL PROTECTED] added the comment: 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

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Changes by Sean Reifschneider [EMAIL PROTECTED]: -- assignee: - fdrake nosy: +fdrake priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2174 __ ___

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

New submission from Yitz Gale: In the documentation for xml.sax.xmlreader.InputSource objects (section 8.12.4 of the Library Reference) we find that users of InputSource objects should use the following sequence to get their input data: 1. If the InputSource has a character stream, use that. 2.

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Yitz Gale added the comment: See also: #1483 and #2175. -- components: +Unicode __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2174 __ ___ Python-bugs-list mailing list

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Yitz Gale added the comment: Hmm. When getSourceEncoding() is None, there needs to be some way for the parser to distinguish between the cases where it is getting pre-decoded Unicode through a character stream, or where it is getting a byte stream with an unspecified encoding. In the latter

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Yitz Gale added the comment: So I think there are two possibilities: 1. Use a special value for getSourceEnconding(), like unicode, to indicate that this is a unicode character stream and not a byte stream. 2. Provide yet another method in the XMLReader interface: sourceIsCharacterStream(),

[issue2174] xml.sax.xmlreader does not support the InputSource protocol

Yitz Gale added the comment: Subclass of XMLReader would be needed, not InputStream. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2174 __ ___ Python-bugs-list mailing list