➜
This issue trackerhas been migrated toGitHub, and is currentlyread-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.
Created on2017-04-12 13:42 byvstinner, last changed2022-04-11 14:58 byadmin. This issue is nowclosed.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 1236 | merged | vstinner,2017-04-21 12:08 | |
| Messages (7) | |||
|---|---|---|---|
| msg291554 -(view) | Author: STINNER Victor (vstinner)* | Date: 2017-04-12 13:42 | |
The issue#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:http://bugs.python.org/issue26530#msg291551So I propose to make the 3 newly added functions public and document them:* _PyTraceMalloc_Track()* _PyTraceMalloc_Untrack()* _PyTraceMalloc_GetTraceback() | |||
| msg291556 -(view) | Author: Julian Taylor (jtaylor) | Date: 2017-04-12 13:48 | |
I am not sure if _PyTraceMalloc_GetTraceback really needs to be a public function.Exposing the tracing information should probably just go over python interfaces. | |||
| msg291557 -(view) | Author: STINNER Victor (vstinner)* | Date: 2017-04-12 14:11 | |
What's the status in numpy? Is the current numpy release able to use CPython 3.6 tracemalloc private functions? | |||
| msg291558 -(view) | Author: Julian Taylor (jtaylor) | Date: 2017-04-12 14:14 | |
With this changeset it would:https://github.com/numpy/numpy/pull/8885 | |||
| msg292029 -(view) | Author: STINNER Victor (vstinner)* | Date: 2017-04-21 12:09 | |
@jtaylor: Ok, I createdhttps://github.com/python/cpython/pull/1236 | |||
| msg296463 -(view) | Author: STINNER Victor (vstinner)* | Date: 2017-06-20 15:46 | |
New changeset5ea4c0677389ead2eee759958694cff2c65834a7 by Victor Stinner in branch 'master':bpo-30054: Expose tracemalloc C API (#1236)https://github.com/python/cpython/commit/5ea4c0677389ead2eee759958694cff2c65834a7 | |||
| msg296464 -(view) | Author: STINNER Victor (vstinner)* | Date: 2017-06-20 15:47 | |
I merged my PR: the future Python 3.7 will provide a public C API to track memory allocations. | |||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:45 | admin | set | github: 74240 |
| 2017-06-20 15:47:31 | vstinner | set | status: open -> closed resolution: fixed messages: +msg296464 stage: resolved |
| 2017-06-20 15:46:39 | vstinner | set | messages: +msg296463 |
| 2017-04-21 12:09:03 | vstinner | set | messages: +msg292029 |
| 2017-04-21 12:08:44 | vstinner | set | pull_requests: +pull_request1354 |
| 2017-04-12 14:14:29 | jtaylor | set | messages: +msg291558 |
| 2017-04-12 14:11:10 | vstinner | set | messages: +msg291557 |
| 2017-04-12 13:48:46 | jtaylor | set | messages: +msg291556 |
| 2017-04-12 13:42:25 | vstinner | create | |