RetroSearch Browse

Fri Sep 21 09:08:28 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-September/121796.html

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.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.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-September/121796.html below:

[Python-Dev] Memoryviews should expose the underlying memory address