You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CPython added PyMem_RawCalloc and PyMem_Calloc in version 3.5. I did not
in include a version guard for 3.4 because PyObject_Calloc was also
added in 3.5 but it's already in this file without a version guard.
I updated comments for other functions to reflect PyMem_Calloc but not
PyMem_RawCalloc to match comments' currently only referencing
PyMem_Malloc and friends.
I did not modify Cython/Utility/ModuleSetupCode.c, where
PyMem_RawMalloc, PyMem_RawRealloc, and PyMem_RawFree are #defined for
Python 3.3 because (a) I couldn't figure out where these were being used
and (b) they're defined to their non-raw versions, which strikes me as
dangerous since the Raw versions allow use without the GIL but the
non-Raw versions do not.
Finally, I updated the tests in cpython_capi.pyx. I'm never sure when
compilers decide code is dead and just ignore it, so I tried actually to
write to the memory and return data from it. I can't figure out how to
run Cython's tests, so... fingers crossed.
While
cpython.mem
contains the other raw allocators, it is missingPyMem_RawCalloc
.The text was updated successfully, but these errors were encountered: