[Python-Dev] Documenting the ssize_t Python C API changes

Jeremy Hylton jeremy at alum.mit.edu
Tue Mar 21 19:06:29 CET 2006

On 3/21/06, M.-A. Lemburg <mal at egenix.com> wrote:
> Don't you think developers are capable enough to judge for
> themselves ?
> They might also want to change their extensions to make use
> of the new possibilities, so a list of APIs taking Py_ssize_t
> parameters on input would be handy to check where there's
> potential for such a change in their code.
> Perhaps we should have three lists:
> 1. Py_ssize_t output parameters (these need changes)
> 2. Py_ssize_t return values (these need overflow checks)
> 3. Py_ssize_t input parameters (these can be used to enhance
>    the extension)

It sounds more like the PEP should list these three categories and
tell developers that they need to inspect their code for instances of
them and fix them in the appropriate way.  Perhaps with an example of


More information about the Python-Dev mailing list