[Python-Dev] PEP 454 - tracemalloc - accepted

Victor Stinner victor.stinner at gmail.com
Sat Nov 23 13:02:37 CET 2013


2013/11/21 Charles-François Natali <cf.natali at gmail.com>:
> I'm happy to officially accept PEP 454 aka tracemalloc.
> The API has substantially improved over the past weeks, and is now
> both easy to use and suitable as a fundation for high-level tools for
> memory-profiling.

I pushed the implementation of he PEP 454 (tracemalloc):

Just after that, I pushed a change in the API to fix a bug:
"Issue #18874: Remove tracemalloc.set_traceback_limit()"

Changing the traceback limit while tracemalloc is tracing can leads to
bugs or weird behaviour. So I added an option nframe parameter to
start instead.

I'm sorry, there are pending comments in the issue. I got many reviews
the last days, I didn't have time to address them yet. I prefer to
push the code before the beta1 because this version marks the feature
freeze and I expect more feedback if the module is included in the
release. I consider that the comments doesn't change the public API
(except the removal of set_tracemalloc_limit which is already done)
and so can be addressed later.

Anyway, thanks to everyone who helped me to build a better tracemalloc module!

And don't hesitate to continue to review the code and test the module.

I will try to write an article for the Python Insider blog to show
some examples of usage of the tracemalloc module. It would be nice to
have similar articles for the other PEPs implemented in Python 3.4,
before the release of Python 3.4!


More information about the Python-Dev mailing list