[Python-Dev] Memoryviews should expose the underlying memory address (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Fri Sep 21 09:08:28 CEST 2012
- Previous message: [Python-Dev] Memoryviews should expose the underlying memory address
- Next message: [Python-Dev] Memoryviews should expose the underlying memory address
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Sep 21, 2012 at 4:12 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Nick Coghlan wrote:
I'm fine with exposing a memoryview.bufferaddress 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.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Memoryviews should expose the underlying memory address
- Next message: [Python-Dev] Memoryviews should expose the underlying memory address
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]