On 9/20/06, Adam Olsen <[EMAIL PROTECTED]> wrote: > Before we can decide on the internal representation of our unicode > objects, we need to decide on their external interface. My thoughts > so far:
Let me cut this short. The external string API in Py3k should not change or only very marginally so (like removing rarely used useless APIs or adding a few new conveniences). The plan is to keep the 2.x API that is supported (in 2.x) by both str and unicode, but merge the twp string types into one. Anything else could be done just as easily before or after Py3k. OTOH, if you want to start to gather requirements for the bytes API, now is the time. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
