RetroSearch Browse

Mon Aug 13 23:25:14 CEST 2007 · https://mail.python.org/pipermail/python-dev/2007-August/074157.html

-----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-----

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2007-August/074157.html below:

[Python-Dev] Python 3000: confused about str8, str, bytes