Message124167
> That's because the new buffer protocol doesn't define ownership of
> Py_buffer structs. As a result, nothing can be assumed at to which
> piece of code is responsible for allocation and deallocation of
> related memory areas (such as shapes and strides arrays).
I was just chatting to Travis about this; he suggested that the 'internal' field of the Py_buffer struct might be used to record who's responsible for deallocation of shape and stride arrays. |
|
Date |
User |
Action |
Args |
2010-12-17 00:19:09 | mark.dickinson | set | recipients:
+ mark.dickinson, teoliphant, ncoghlan, kermode, pitrou |
2010-12-17 00:19:09 | mark.dickinson | set | messageid: <1292545149.15.0.061493271366.issue9990@psf.upfronthosting.co.za> |
2010-12-17 00:19:06 | mark.dickinson | link | issue9990 messages |
2010-12-17 00:19:06 | mark.dickinson | create | |
|