[Python-3000] On PEP 3116: new I/O base classes

[Nick Coghlan]

Bill Janssen wrote:
>> I'm not sure I 100% understand what you mean by "normalization policy"
>> (Q).  Could you give an example?
> 
> I was speaking of the 4 different normalization forms for Unicode,
> which can produce different code-point sequences.  Since "strings" in
> Python-3000 aren't really strings, but instead are immutable
> code-point sequences, this means that any byte-to-string
> transformation which doesn't specify this can produce different
> strings from the same bytes without violating its constraints.

A given codec won't randomly decide to change its normalisation policy, 
though - so when you pick the codec, you're picking the normalisation as 
well.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
             http://www.boredomandlaziness.org