Message204619
| Author |
Jim.Jewett |
| Recipients |
Jim.Jewett, amaury.forgeotdarc, belopolsky, eric.snow, neologix, python-dev, rhettinger, tim.peters, vajrasky, vstinner |
| Date |
2013年11月27日.22:17:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1385590654.05.0.265217919982.issue18874@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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? |
|