Martin v. Löwis <mar...@v.loewis.de> added the comment: > Are you serious? This sounds like a py4k idea. Can you give us a > hint on what the new representation will be?
I'm thinking about an approach of a variable representation: one, two, or four bytes, depending on the widest character that appears in the string. I think it can be arranged to make this mostly backwards-compatible with existing APIs, so it doesn't need to wait for py4k, IMO. OTOH, I'm not sure I'll make it for 3.3. > Meanwhile, what it your > recommendation for application developers? Should they attempt to fix > the code that assumes len(chr(i)) == 1? Should text processing > applications designed to run on a narrow build simply reject non-BMP > text? Should application writers avoid using str.isxyz() methods? Given that this is vaporware: proceed as if that idea didn't exist. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10542> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
