[Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
v+python at g.nevcal.com
Wed Apr 29 05:29:16 CEST 2009
On approximately 4/28/2009 7:40 PM, came the following characters from
the keyboard of R. David Murray:
> On Tue, 28 Apr 2009 at 13:37, Glenn Linderman wrote:
>> C. File on disk with the invalid surrogate code, accessed via the str
>> interface, no decoding happens, matches in memory the file on disk
>> with the byte that translates to the same surrogate, accessed via the
>> bytes interface. Ambiguity.
> Unless I'm missing something, one of these is type str, and the other is
> type bytes, so no ambiguity.
You are missing that the bytes value would get decoded to a str; thus
both are str; so ambiguity is possible.
Glenn -- http://nevcal.com/
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
More information about the Python-Dev