-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Nov 23, 2008, at 6:16 PM, Gregory P. Smith wrote:
On Sat, Nov 22, 2008 at 11:51 AM, Brett Cannon <[EMAIL PROTECTED]>
wrote:
On Sat, Nov 22, 2008 at 06:29, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Nov 22, 2008, at 4:05 AM, Martin v. Löwis wrote:
I just noticed that the Python 3 C API still contains
PY_SSIZE_T_CLEAN.
This macro was a transition mechanism, to allow extensions to use
Py_ssize_t in PyArg_ParseTuple, while allowing other module
continue
to use int.
In Python 3, I would like the mechanism, making Py_ssize_t the only
valid data type for size in, say, s# parsers.
Is it ok to still change that?
Given that we just released the last planned candidate, I'd say it
was
too
late to change this for Python 3.0.
But we can at least document that the macro is a gone as soon as 3.0
final is out the door.
-Brett
I'll commit the following update to the py3k docs if nobody
objects. As it
is now, the only mention of PY_SSIZE_T_CLEAR at all is in whatsnew/
2.5.rst.
This officially documents it and mentions that it is going away to
be always
on in the future. I'm assuming in 3.1 but I just left it as "a future
version" to not commit to that. At least the py3k docs encourage
use of s*
rather than s#.
Perfect, thanks.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSSqiuXEjvBPtnXfVAQIh3QP/WNw2mwCATAZ6oqI1vB0K37R+JZmV/qVZ
8CjgwrJcBPolFB9DYZ8AO6rvdGwnqRf2a/3fCg2ZRPQuJgJh1lPeFXuxm92Qn9fJ
aXS0ph1i4r467LyYMqhZYcHRGOATQwc31phd2YHvkeYZCdijq3sPN7ZCq40LDQRQ
sxJj+GkjkTE=
=ejGW
-----END PGP SIGNATURE-----
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
