Nick Coghlan <ncoghlan <at> gmail.com> writes: > > Actually, I think your suggested scheme for the one-dimensional case > shows the way forward: ownership of the shape and strides memory belongs > to the object issuing the Py_buffer struct, and that object needs to > deal with it when the buffer is released. Defining a larger memory chunk > with the Py_buffer as the first item and the shape and stride info > tacked onto the end and returning that from PyObject_GetBuffer() means > that the shape/stride info will be released automatically when the view > is released via PyBuffer_Release().
Ok, so another question: given that this will change the Py_buffer layout a bit, can it go into 3.0.1 and 2.6.2? _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
