Any reason why cStringIO in 2.5 behaves different from 2.4?

Stefan Behnel stefan.behnel-n05pAM at web.de
Sat Jul 28 19:49:08 CEST 2007


Stefan Scholl wrote:
> Chris Mellon <arkanes at gmail.com> wrote:
>> On 7/26/07, Stefan Scholl <stesch at no-spoon.de> wrote:
>>> Chris Mellon <arkanes at gmail.com> wrote:
>>>> XML is not a string. It's a specific type of bytestream. If you want
>>>> to work with XML, then generate well-formed XML in the correct
>>>> encoding. There's no reason you should have an XML document (as
>>>> opposed to values extracted from that document) in unicode objects at
>>>> all.
>>> The affected method in xml.sax is called parseString()
>> The imprecision of the english language has caused greater problems
>> than this. Since you've now had everything clarified for you, and the
>> imprecision is resolved, I'm sure that this won't be a problem again.
> 
> 
> Right. I now know that xml.sax's parseString() has undocumented
> implementation dependent behavior. That there are libraries (not
> included with Python) which can parse Unicode strings. And that
> the reason to change cStringIO's behavior is acceptable.
> 
> But the style of the answers makes me wonder if I should report
> the bug in xml.sax (or its documentation) or just ignore it.

Note that PyXML is no longer actively maintained, so it's unlikely that
reporting the bug would get you a version that raises an exception when
passing a unicode string *independent of the Python version*.

Besides, the bug has been fixed in Python 2.5 already.

Stefan



More information about the Python-list mailing list