On Nov 29, 2006, at 1:09, Travis Oliphant wrote: > You can > > #define PY_SSIZE_T_MIN INT_MIN > #define PY_SSIZE_T_MAX INT_MAX > > before including the NumPy header file and it will by-pass the typedef > for Py_ssize_t.
Interesting. Is that a test that would work for distinguishing Python 2.5 from its predecessors as well? In other words, is that a test that one could add to every header file to avoid problems? That's what I am looking for... Konrad. -- --------------------------------------------------------------------- Konrad Hinsen Centre de Biophysique Moléculaire, CNRS Orléans Synchrotron Soleil - Division Expériences Saint Aubin - BP 48 91192 Gif sur Yvette Cedex, France Tel. +33-1 69 35 97 15 E-Mail: [EMAIL PROTECTED] --------------------------------------------------------------------- _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
