[Python-Dev] Py_ssize_t (original) (raw)

Barry Warsaw barry at python.org
Tue Feb 20 14🔞45 CET 2007

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Feb 20, 2007, at 4:47 AM, Raymond Hettinger wrote:

The other area where I expected to hear wailing and gnashing of teeth is users compiling with third-party extensions that haven't been updated to a Pyssizet API and still use longs. I would have expected some instability due to the size mismatches in function signatures -- the difference would only show- up with giant sized data structures -- the bigger they are, the harder they fall. OTOH, there have not been any compliants either -- I would have expected someone to submit a patch to pyport.h that allowed a #define to force Pyssizet back to a long so that the poster could make a reliable build that included non-updated third-party extensions.

When I did an experimental port of our big embedded app to Python
2.5, that's (almost) exactly what I did. I didn't add the #define to
a Python header file, but to our own and it worked pretty well,
IIRC. I never went farther than the experimental phase though.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRdr1QHEjvBPtnXfVAQIO0wP5Adr7c467NFn5fjmvcAemtvjg+3Tri0qV SHI6LF88tSYkxKLezTojXPFQ+kYTjgz1yLa1KuQ6W9Q8dhiKGUVu7ZqFT12IGcIV n6Yf0htkpGmq/3G7m7D7yWHQrQE3Ce3+f6tI/4aL5eQ3mgdo1y828sY/sCCc4fTC Ln2gSad6g/M= =QQ5y -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list