Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Well, this is not a bug in itself. Memoryview objects are designed to give access to a memory area backed by another object - they don't "own" the memory by themselves (in the sense that you e.g. own a reference to a PyObject).
Please note by the way that the Py_buffer struct now has a reference to the original object, the "obj" field. PyBuffer_FillInfo() will incref it, and PyBuffer_Release() will decref it again. However, it you set this field to NULL, you are responsible for doing your own reference management. I agree that it may be nice to support your use case, but I'm not sure what the semantics should be. For clarity, perhaps it should be a derived class of memoryview. ---------- type: resource usage -> feature request _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3608> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
