Message 204621 - 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	Jim.Jewett, neologix, vstinner
Date	2013-11-27.22:18:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1385590738.28.0.662362408698.issue19818@psf.upfronthosting.co.za>
In-reply-to

Content
And copy of his second message msg204619: Drat: forgot one at line 277 .. function:: get_traced_memory() Get the current size and maximum size of memory blocks traced by the :mod:`tracemalloc` module as a tuple: ``(size: int, max_size: int)``. I have a tendency to read "maximum size" as the most it is willing/able to trace, rather than the most it has traced at a single time so far. I therefore prefer "peak_size". Also, this doesn't suggests that the object is strictly a tuple, and that results.size or results.peak_size will not work; is that intentional?

And copy of his second message msg204619:

Drat:  forgot one at line 277


.. function:: get_traced_memory()

   Get the current size and maximum size of memory blocks traced by the
   :mod:`tracemalloc` module as a tuple: ``(size: int, max_size: int)``.

I have a tendency to read "maximum size" as the most it is willing/able to trace, rather than the most it has traced at a single time so far.  I therefore prefer "peak_size".

Also, this doesn't suggests that the object is strictly a tuple, and that results.size or results.peak_size will not work; is that intentional?

History
Date	User	Action	Args
2013-11-27 22:18:58	vstinner	set	recipients: + vstinner, neologix, Jim.Jewett
2013-11-27 22:18:58	vstinner	set	messageid: <1385590738.28.0.662362408698.issue19818@psf.upfronthosting.co.za>
2013-11-27 22:18:58	vstinner	link	issue19818 messages
2013-11-27 22:18:58	vstinner	create