[Python-Dev] Re: test_unicode_file failing on Mac OS X (original) (raw)
Martin v. Löwis martin at v.loewis.de
Wed Dec 10 12:16:15 EST 2003
- Previous message: [Python-Dev] Re: test_unicode_file failing on Mac OS X
- Next message: [Python-Dev] release23-maint branch CLOSED for release (was Re: 2.3.3 cycle)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Scott David Daniels <Scott.Daniels at Acm.Org> writes:
Still not disgusting, but unicode strings must hash equal to the corresponding "plain" string. I am not certain about this requirement for non-ASCII characters, but I expect we are stuck with matching hashes in the range ord(' ') through ord('~') and probably for all character values from 0 through 127.
Strictly speaking, unicode and byte strings must hash equal if they convert to each other through the system encoding. As a side effect, this really means that the system encoding currently must be ASCII, as the current hash function won't otherwise hash equal (latin-1 may also be correct as the system encoding).
Fortunately, plain ASCII strings are in all applicable normal forms (NFC, NFKC, NFD, NFKD).
Regards, Martin
- Previous message: [Python-Dev] Re: test_unicode_file failing on Mac OS X
- Next message: [Python-Dev] release23-maint branch CLOSED for release (was Re: 2.3.3 cycle)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]