[issue10001] ~Py_buffer.obj field is undocumented, though not hidden

Nick Coghlan added the comment: Closing as a dupe of 10181, but transferring Lenard's comments over there. -- resolution: -> duplicate status: open -> closed superseder: -> Problems with Py_buffer management in memoryobject.c (and elsewhere?) ___

[issue10001] ~Py_buffer.obj field is undocumented, though not hidden

Changes by Antoine Pitrou : -- nosy: +mark.dickinson, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10001] ~Py_buffer.obj field is undocumented, though not hidden

Lenard Lindstrom added the comment: This will work for bf_getbuffer, though having PyObject_GetBuffer set the obj field before passing it to the callback might be safer. Also, this does not address the case with wrapper types like memoryview. What happens if ~Py_buffer.obj is not visited in t

[issue10001] ~Py_buffer.obj field is undocumented, though not hidden

Antoine Pitrou added the comment: The recommended way is to use PyBuffer_FillInfo() (and then fill in any additional data if necessary), which will set the pointer and incref it itself. I agree all this is a bit poorly documented. -- assignee: -> d...@python components: +Documentatio

[issue10001] ~Py_buffer.obj field is undocumented, though not hidden

New submission from Lenard Lindstrom : Python 3.2a2+ (py3k:85072M, Sep 29 2010, 12:11:17) (from SVN) [GCC 4.4.5 20100728 (prerelease)] on linux2 (Debian squeeze) The ~Py_buffer.obj field is undocumented. Yet memoryview, that acts as a wrapper, includes the field in gc traversal. Also, if the fi