-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose tracemalloc C API to track/untrack memory blocks #74240
Comments
The issue bpo-26530 added a private C API to manually track/untrack memory blocks in tracemalloc. I was just validated by Julian Taylor who confirms that the API works as expected: So I propose to make the 3 newly added functions public and document them:
|
I am not sure if _PyTraceMalloc_GetTraceback really needs to be a public function. |
What's the status in numpy? Is the current numpy release able to use CPython 3.6 tracemalloc private functions? |
With this changeset it would: |
I merged my PR: the future Python 3.7 will provide a public C API to track memory allocations. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: