Greg Ewing wrote: > In any case, I think it should be possible to implement > either version without the memoryview having to own > more than one Py_buffer and one set of shape/strides > at a time. Slicing the memoryview creates another > memoryview with its own Py_buffer and shape/strides.
The important point is that the shape information in the Py_buffer filled in by the underlying object is the shape of *that* object. Except in the trivial case where the memoryview is exposing the entire underlying data buffer, the shape information in the Py_buffer has nothing to do with the shape of the memoryview object itself. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ 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
