On Fri, Sep 21, 2012 at 4:12 PM, Greg Ewing firstname.lastname@example.org wrote:
Nick Coghlan wrote:
I'm fine with exposing a memoryview.buffer_address attribute in 3.4.
What about objects whose buffer address can change when the buffer isn't locked?
Managing the lifecycle issues will be up to the application. If they let the memoryview object go away, then the buffer it references may also go away. This isn't any different from the situation with array.buffer_info() - the address from that is only valid as long as the array object itself is still around.