[issue9789] Explicit buffer release for memoryview objects

Changes by Nick Coghlan : -- superseder: -> Add context manager protocol to memoryviews ___ Python tracker ___ ___ Python-bugs-list ma

[issue9789] Explicit buffer release for memoryview objects

Changes by Nick Coghlan : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9789] Explicit buffer release for memoryview objects

Nick Coghlan added the comment: Thanks for that link. Compared to what either of us managed in the original thread, I think my first post here better articulates why the ability to explicitly release the buffer is important - not because of general memory usage, but because the object owning

[issue9789] Explicit buffer release for memoryview objects

Antoine Pitrou added the comment: See the context management patch at #9757. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9789] Explicit buffer release for memoryview objects

Nick Coghlan added the comment: The test suite actually does force a GC collection cycle, so the test may be more portable than I first thought, but the need to do that suggests an explicit buffer release API may be a more appropriate solution. --

[issue9789] Explicit buffer release for memoryview objects

New submission from Nick Coghlan : memoryview objects currently offer no way to explicitly release the underlying buffer. This may cause problems for mutable objects that are locked while PEP 3118 buffer references remain unreleased (e.g. in 3.2, io.BytesIO supports getbuffer() for direct acc