Hi, 2013/11/21 Charles-François Natali <cf.nat...@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): http://hg.python.org/cpython/rev/6e2089dbc5ad Just after that, I pushed a change in the API to fix a bug: http://hg.python.org/cpython/rev/66db0c66a6ee "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. http://bugs.python.org/issue18874 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! http://blog.python.org/ Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
