When I said it wasn't decided I was totally serious. No decision has been reached.
However, I strongly recommend that you try to write all your code using PyUnicode and PyBytes, avoiding PyString completely. Even if str8/PyString will remain in existence, it will be a last resort type for backwards compatibility. We *may* at some point rename PyUnicode to PyString (or PyText, to avoid confusion), but don't count on this. If we do, we'll provide a tool or service to do the conversion for you. --Guido On 8/13/07, Gerhard Häring <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I maintain the sqlite module in the standard library, which makes heavy use > of PyString_* C API. Now I've made it work under Python 3000 insofar as > tests pass, but the new Python string semantics mean I have more work to do > here and make some API choices. > > I've read in another thread that the future of str8 is not decided yet. To > be honest I was confused when I saw it first, it's documented nowhere as > far as I can see. > > Is that decided yet? Is str8 going away? > > What will happen with the Python C API? Will PyString_* become what > PyUnicode_* is in Python 2.x? > > - -- Gerhard > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGwMw6dIO4ozGCH14RAoyEAJ0eoqZ8gSqKh5/HIXxhbG5xpMedLgCgquQV > Qv+CGyoD8eSXaoAKzn2WBSM= > =w4HB > -----END PGP SIGNATURE----- > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
