-----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.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSSgXLnEjvBPtnXfVAQKEVwP7BMofjGhTTfQ847X767ONgkt7gqr6+jeS
Fv8y0NR7quMAU6LAsdg3ScpDhXItwiefGGAkaqGojwQKxAcy0xTWVNnhAtytQ3Xc
ZuyhFng++jl0qLz3+s3/IUl+gVM/PPlnjf+Kh4dHrjpUW8yuq3wOMCdpL6DAS9xA
xI9wiHHoXeU=
=WLHV
-----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
