[Python-Dev] Allocation of shape and strides fields in Py_buffer (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue Dec 9 15:56:42 CET 2008
- Previous message: [Python-Dev] Allocation of shape and strides fields in Py_buffer
- Next message: [Python-Dev] Allocation of shape and strides fields in Py_buffer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antoine Pitrou <solipsis pitrou.net> writes:
> The first is that memoryview is treating the len field in the > Pybuffer struct as the number of objects in the view in a few places > instead of as the total number of bytes being exposed (it is actually > the latter, as defined in PEP 3118). I don't understand the difference between "the number of objects in the view" and "the total number of bytes being exposed". For me it should be the same and the "buf" and "len" fields in the Pybuffer should be usable by any other C function, otherwise they are useless.
Sorry, I had misread your message. Yes, indeed "len" should the number of bytes, not the number of objects. This is also solved as part of the patch I proposed in the aforementioned bug entry.
Regards
Antoine.
- Previous message: [Python-Dev] Allocation of shape and strides fields in Py_buffer
- Next message: [Python-Dev] Allocation of shape and strides fields in Py_buffer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]