[Python-Dev] Allocation of shape and strides fields in Py_buffer (original) (raw)

Antoine Pitrou solipsis at pitrou.net
Tue Dec 9 12:21:43 CET 2008

Alexander Belopolsky <alexander.belopolsky gmail.com> writes:

I did not follow numpy development for the last year or more, so I won't qualify as "the numpy folks," but my understanding is that numpy does exactly what Nick recommended: the viewed object owns shape and strides just as it owns the data. The viewing object increases the reference count of the viewed object and thus assures that data, shape and strides don't go away prematurely.

That doesn't work if e.g. you take a slice of a memoryview object, since the shape changes in the process. See http://bugs.python.org/issue4580

More information about the Python-Dev mailing list