[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Antoine Pitrou
report at bugs.python.org
Sun Feb 13 20:42:18 CET 2011
Antoine Pitrou <pitrou at free.fr> added the comment:
That said:
> Having the memoryview "own" the exported buffer would be a simple
> solution to the above issue.
If you can implement that without exhibing the issues we discussed above (e.g. O(N) memory consumption when doing repetitive slicing), then why not.
Also, thanks for the patch. Please refrain from spurious formatting changes, though.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10181>
_______________________________________
More information about the Python-bugs-list
mailing list