This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, georg.brandl, schiotz
Date 2008-10-15.11:44:12
SpamBayes Score 0.00012449766
Marked as misclassified No
Message-id <1224071053.64.0.0402246876242.issue4129@psf.upfronthosting.co.za>
In-reply-to
Content
I think the Py_ssize_t change is clearly documented in the "What's new"
document:
http://docs.python.org/whatsnew/2.5.html#pep-353-using-ssize-t-as-the-index-type
This paragraph also links to:
http://www.python.org/dev/peps/pep-0353/#doesn-t-this-break-much-code
which happens to mention the incompatibility in the slice API.

Didn't you get any compilation warning?

I suggest to use a newer version of Scientific Python: 2.7 at least uses
Py_ssize_t throughout its code.
History
Date User Action Args
2008-10-15 11:44:13amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, georg.brandl, schiotz
2008-10-15 11:44:13amaury.forgeotdarcsetmessageid: <1224071053.64.0.0402246876242.issue4129@psf.upfronthosting.co.za>
2008-10-15 11:44:12amaury.forgeotdarclinkissue4129 messages
2008-10-15 11:44:12amaury.forgeotdarccreate