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 eryksun
Recipients David Heffernan, amaury.forgeotdarc, belopolsky, coderforlife, eryksun, ezio.melotti, loewis, meador.inge
Date 2017-05-10.11:51:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494417075.27.0.700728162469.issue16865@psf.upfronthosting.co.za>
In-reply-to
Content
In older versions of ctypes, before it was added to the standard library, the underlying length field was a C int, and CArrayType_new used the PyInt_AS_LONG macro. ctypes was added to the standard library in 2.5, by which time the length field is Py_ssize_t, but CArrayType_new still used the PyInt_AS_LONG macro. That's still the case in 2.7. Python 3 changed this to call PyLong_AsLongAndOverflow, but apparently Christian Heimes didn't consider fixing this properly to use Py_ssize_t:

https://hg.python.org/cpython/rev/612d8dea7f6c

David, maybe there's a workaround for your use case, if you can provide some more details.
History
Date User Action Args
2017-05-10 11:51:15eryksunsetrecipients: + eryksun, loewis, amaury.forgeotdarc, belopolsky, ezio.melotti, meador.inge, coderforlife, David Heffernan
2017-05-10 11:51:15eryksunsetmessageid: <1494417075.27.0.700728162469.issue16865@psf.upfronthosting.co.za>
2017-05-10 11:51:15eryksunlinkissue16865 messages
2017-05-10 11:51:15eryksuncreate