Nick Coghlan <ncoghlan <at> gmail.com> writes: > > Parts 2 and 3, being the memoryview API and support for the new protocol > in the builtin types are the parts that are currently restricted to > simple linear memory views. > > That's largely because parts 2 and 3 are somewhat use case challenged: > the key motivation behind PEP 3118 was so that libraries like NumPy, PIL > and the like would have a common standard for data interchange.
If I understand correctly, one of the motivations behind memoryview() is to replace buffer() as a way to get cheap slicing without memory copies (it's used e.g. in the C IO library). I don't know whether the third-party types mentioned above could also benefit from that. Regards Antoine. _______________________________________________ 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
