Mark Dickinson <dicki...@gmail.com> added the comment: > That's because the new buffer protocol doesn't define ownership of > Py_buffer structs. As a result, nothing can be assumed at to which > piece of code is responsible for allocation and deallocation of > related memory areas (such as shapes and strides arrays).
I was just chatting to Travis about this; he suggested that the 'internal' field of the Py_buffer struct might be used to record who's responsible for deallocation of shape and stride arrays. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9990> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
