[issue6659] buffer c-api: memoryview object documentation

Benjamin Peterson added the comment: Fixed in r74551. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pytho

[issue6659] buffer c-api: memoryview object documentation

Alexey Shamrin added the comment: Antoine, it seems, this sentence was taken literally from PEP3118 (http://www.python.org/dev/peps/pep-3118/#new-c-api-calls-are-proposed). PEP authors discussed if __builtins__.buffer should be removed. I agree, old __builtins__.buffer should not be mentioned h

[issue6659] buffer c-api: memoryview object documentation

Antoine Pitrou added the comment: Well, the terminology in these docs is not very precise and helpful. There are two things here: - the buffer /struct/ a.k.a Py_buffer, which can only be used from C code and using the dedicated "new buffer API" - the memoryview, which is a Python object (a PyObj

[issue6659] buffer c-api: memoryview object documentation

Georg Brandl added the comment: Benjamin is listed as the section author. -- assignee: georg.brandl -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ _

[issue6659] buffer c-api: memoryview object documentation

New submission from Alexey Shamrin : "A memoryview object is an extended buffer object that could replace the buffer object (but doesn’t have to as that could be kept as a simple 1-d memoryview object)." Well, buffer object was dropped Python 3, wasn't it? http://docs.python.org/dev/py3k/c-api/