Message250913
Serhiy contends that calling newblock() can mutate the deque (its only external call is PyMem_Malloc()). I'm trying understand how that could be possible if it is just a thin wrapper around malloc.
Before gumming-up the code in an effort to avoid calling newblock(), I want to understand whether there is an actual issue here and if so whether PyMem_RawMalloc() would solve the problem directly. |
|
Date |
User |
Action |
Args |
2015-09-17 19:24:33 | rhettinger | set | recipients:
+ rhettinger, vstinner, serhiy.storchaka |
2015-09-17 19:24:33 | rhettinger | set | messageid: <1442517873.15.0.317914448857.issue25135@psf.upfronthosting.co.za> |
2015-09-17 19:24:33 | rhettinger | link | issue25135 messages |
2015-09-17 19:24:32 | rhettinger | create | |
|