[issue9990] PyMemoryView_FromObject alters the Py_buffer after calling PyObject_GetBuffer when ndim 1
Nick Coghlan
report at bugs.python.org
Fri Jan 7 10:39:49 CET 2011
Nick Coghlan <ncoghlan at gmail.com> added the comment:
As per the discussion over in issue #10181, I've changed my position on this issue.
Since the PEP isn't explicit on the exact semantics here, I think we should be guided by the memoryview behaviour and make it official that bf_releasebuffer implementations shouldn't trust the contents of the passed in Py_buffer struct. Instead, if that information is important, the exporter should create an internal data structure that preserves the necessary detail and merely use the Py_buffer address as an identifier to locate the internal copy.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9990>
_______________________________________
More information about the Python-bugs-list
mailing list