Message 272895 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	Mark.Shannon, aniawsz, larry, vstinner
Date	2016-08-17.00:31:04
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1471393865.33.0.125022250719.issue24648@psf.upfronthosting.co.za>
In-reply-to

Content
In Python 3.6, PyMem_Malloc() is now an alias to PyObject_Malloc(), both functions use the pymalloc allocator: see the issue #26249. This issue can now be closed. -- Note: I created the issue #26249 when I saw the good results of the issue #23601. In fact, I had the idea when I wrote tracemalloc, but I chose to defer the idea because some people expected regressions. PYTHONMALLOC=debug should now help to find and debug issues: https://docs.python.org/dev/whatsnew/3.6.html#pythonmalloc-environment-variable

In Python 3.6, PyMem_Malloc() is now an alias to PyObject_Malloc(), both functions use the pymalloc allocator: see the issue #26249.

This issue can now be closed.

--

Note: I created the issue #26249 when I saw the good results of the issue #23601. In fact, I had the idea when I wrote tracemalloc, but I chose to defer the idea because some people expected regressions. PYTHONMALLOC=debug should now help to find and debug issues:
https://docs.python.org/dev/whatsnew/3.6.html#pythonmalloc-environment-variable

History
Date	User	Action	Args
2016-08-17 00:31:05	vstinner	set	recipients: + vstinner, larry, Mark.Shannon, aniawsz
2016-08-17 00:31:05	vstinner	set	messageid: <1471393865.33.0.125022250719.issue24648@psf.upfronthosting.co.za>
2016-08-17 00:31:05	vstinner	link	issue24648 messages
2016-08-17 00:31:04	vstinner	create