On 16 Jun 2013 10:54, "Victor Stinner" <victor.stin...@gmail.com> wrote: > > 2013/6/15 Antoine Pitrou <solip...@pitrou.net>: > > Moreover, I think you are conflating two issues: the ability to add > > memory allocation hooks (for tracing/debugging purposes), and the > > adaptation to "non-traditional" memory models (whatever that means). > > Those concerns don't necessarily come together. > > In my implementation, both uses case use the same API: > PyMem_SetAllocators(), except that hooks need also > PyMem_GetAllocators().
Right - they're different use cases that share a technical solution, so it makes sense to consider them together. Cheers, Nick. > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
