[Python-Dev] Documenting the ssize_t Python C API changes (original) (raw)

Terry Reedy tjreedy at udel.edu
Tue Mar 21 18:45:44 CET 2006

"M.-A. Lemburg" <mal at egenix.com> wrote in message news:442032D3.8020609 at egenix.com...

Perhaps we should have three lists:

1. Pyssizet output parameters (these need changes) 2. Pyssizet return values (these need overflow checks) 3. Pyssizet input parameters (these can be used to enhance the extension)

If I were an extension writer in a position to need these, I am sure I would prefer the three lists separated. (Where housed would otherwise be pretty irrelevant.) I know I would strongly prefer to have them be separate plain ascii text files linked to as appendixes rather than incorporated into the PEP itself.

I might also like a separate doc (or wiki entry/ies) on updating extension to use Py_ssize_t, with more than one persons experiences, if indeed it it not trivial and straightforward.

Terry Jan Reedy

More information about the Python-Dev mailing list