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 pitrou
Recipients amaury.forgeotdarc, loewis, pitrou, rhettinger, serhiy.storchaka
Date 2013-09-19.18:39:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379615993.2511.25.camel@fsol>
In-reply-to <>
> It's why sys.getsizeof() is a low-level tool. We need high-level tool
> in the stdlib. Even imperfect recursive counting will be better than
> confusing for novices sys.getsizeof().

Ok, but I need to see a satisfying version of "gettotalsizeof" before
I'm convinced (see below).

> Here is improved version of gettotalsizeof():
> >>> gettotalsizeof(gettotalsizeof)
> 60854

Why that big? Does it make sense?

What if say, a large object is "shared" between many small objects?
Should it count towards the memory size of any of those small objects?
What if that object is actually immortal (it is also a module global,
for example)?
Date User Action Args
2013-09-19 18:39:55pitrousetrecipients: + pitrou, loewis, rhettinger, amaury.forgeotdarc, serhiy.storchaka
2013-09-19 18:39:55pitroulinkissue19048 messages
2013-09-19 18:39:55pitroucreate