``get_tracemalloc_memory()`` function:
Get the memory usage in bytes of the ``tracemalloc`` module as a
tuple: ``(size: int, free: int)``.
* *size*: total size of bytes allocated by the module,
including *free* bytes
* *free*: number of free bytes available to store
2013/10/19 Nick Coghlan ncogh...@gmail.com:
Speaking of which... Charles-François, would you be willing to act as
BDFL-Delegate for this PEP? This will be a very useful new analysis tool,
and between yourself and Victor it looks like you'll be able to come up with
a solid API.
I just
On Sat, Oct 19, 2013 at 10:00 AM, Charles-François Natali
cf.nat...@gmail.com wrote:
2013/10/19 Nick Coghlan ncogh...@gmail.com:
Speaking of which... Charles-François, would you be willing to act as
BDFL-Delegate for this PEP? This will be a very useful new analysis tool,
and between
Let it be known to all that Charles-François Natali is hereby appointed
BDFL for this PEP.
On Sat, Oct 19, 2013 at 7:00 AM, Charles-François Natali
cf.nat...@gmail.com wrote:
2013/10/19 Nick Coghlan ncogh...@gmail.com:
Speaking of which... Charles-François, would you be willing to act as
Hi,
I plan to push the new tracemalloc module this week-end, before the
next (and last) alpha version, except if someone complains :-) I
prefer to have one month before the first beta to have more time to
test the module. So if a major issue is raised, we may remove the
tracemalloc module before
This looks really nice to me, and splitting it so the core
functionality is in the standard library and there's a separate higher
level tool on PyPI (allowing faster iteration on the analysis
features) is a fine idea.
Cheers,
Nick.
___
Python-Dev
Hi,
I'm happy to see this move forward!
API
===
Main Functions
--
``clear_traces()`` function:
Clear traces and statistics on Python memory allocations, and reset
the ``get_traced_memory()`` counter.
That's nitpicking, but how about just ``reset()`` (I'm probably
2013/10/18 Charles-François Natali cf.nat...@gmail.com:
I'm happy to see this move forward!
Thanks for your reviews. I had some time in my train travel to improve
the implementation.
I removed the call to pthread_atfork(): tasks have been removed, it
now makes sense to keep tracemalloc enabled
On 19 Oct 2013 03:57, Charles-François Natali cf.nat...@gmail.com wrote:
Hi,
I'm happy to see this move forward!
Speaking of which... Charles-François, would you be willing to act as
BDFL-Delegate for this PEP? This will be a very useful new analysis tool,
and between yourself and Victor it
