Stefan Krah <stefan-use...@bytereef.org> added the comment: [The first part of the message again, this time via the web interface.]
Antoine is right, this needs to be fixed. I think that for *practical* purposes, the existing release() method already behaves like a tryrelease() method: >>> b = bytearray(b'123456789') >>> m1 = memoryview(b) >>> m2 = memoryview(m1) >>> m1.release() >>> b.append(1) Traceback (most recent call last): File "<stdin>", line 1, in <module> BufferError: Existing exports of data: object cannot be re-sized >>> So while m1.release() in fact *does* release a buffer, the desired effect (freeing up 'b' for subsequent operations) only happens after also calling m2.release(). This applies to Python and NumPy objects. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10181> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
