Re: Unicode string handling

> What I mean is that if we =define terminators as characters/strings, as I
> thought you suggested, instead of integers (like we do now) we will not be
> able to support terminators that are not representable as characters.

The stated problem was that we allow multiple types for terminators
including integers and strings.  We should only allow one type with
very well defined semantics.  I don't care if it is strings, integers
or sequence of integers.  It should just be consistent.  The secondary
point is that the terminator is not passed to the codecs so it doesn't
matter if Python's codecs leave particular codepoints in or out.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642