> In other words, the allocators are concerned about
> memory, not tracing or anything else that can be done by overriding them.

Ok I now understand that `tracemalloc`'s use of allocator APIs is just an 
implementation detail. Allocator APIs were used for tracing but they are not 
designed for that: which makes perfect sense.

However, I still wonder: is there anyway to support `PyTraceMalloc_Track` API 
without being dependent to `tracemalloc`? I know there is not many memory 
tracing tools but I mean I still feel like there should be a generic way of 
doing this: A very vague example for demonstration:

PyMemHooks_GetAllocators/PyMemHooks_SetAllocators/PyMemHooks_TrackAlloc which 
are public APIs and tracemalloc using them internally instead of allocator APIs?

>Regards from rainy London,
Cheers from a cold Istanbul, :)
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/BBHAJQGIUIBRTW7ZWUYHSP3JACLCTIHS/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to