where to handle python version mismatches?
Y Giridhar Appaji Nag <[email protected]> Tue, 13 May 2008 18:48:21 +0530
| Newsgroups | gmane.comp.web.links |
|---|---|
| Message-ID | <[email protected]> |
Hi, In Python 2.5, PyString_AsStringAndSize takes Py_ssize_t* instead of int* as its last argument. This causes ELinks 0.12 build failures on 64bit archs if Python 2.5 is used for building the Python hooks. I understand that the way to fix this sort of a thing in ELinks is to define a new type (say Py_ssize_t_T) that maps to the right thing. What would be the best place to do it? src/osdep/types.h doesn't look to the right place because I will have to include Python.h (and hence python patchlevel.h) and define Py_ssize_t_T conditionally depending on PY_VERSION_HEX. Or do you suggest that I just fix this in src/scripting/python/hooks.c where PyString_AsStringAndSize is used? i.e. cast the third argument conditionally or declare len conditionally there. Giridhar -- Y Giridhar Appaji Nag | http://appaji.net/ _______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIKZUc4eu+pR04mIcRApAIAJsEFaOQCyyoG+Sn4J4kPD26csAOogCeKUnK 00cMT6qyiNKqEcy+4EfBs6U= =CUnO -----END PGP SIGNATURE-----