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 loewis
Recipients amaury.forgeotdarc, loewis, pitrou, rhettinger, serhiy.storchaka
Date 2013-09-19.18:06:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The problem is that that definition isn't helpful.
> If we ever change itertools.tee to use non-PyObjects internally, s
> suddenly its sys.getsizeof() would have to return much larger numbers 
> despite visible behaviour not having changed at all (and despite the 
> memory overhead being actually lower).

I see no problem with that. If the internal representation changes, nobody should be surprised if sizeof changes.

> I would hope it gives remotely useful information about the passed object.

It certainly does: it reports the memory consumption of the object itself, 
not counting the memory of other objects.

I proposed a precise definition of what "an other object" is. If you don't like it,
please propose a different definition that still allows to automatically sum up the
memory of a graph of objects.
Date User Action Args
2013-09-19 18:06:32loewissetrecipients: + loewis, rhettinger, amaury.forgeotdarc, pitrou, serhiy.storchaka
2013-09-19 18:06:32loewissetmessageid: <>
2013-09-19 18:06:32loewislinkissue19048 messages
2013-09-19 18:06:32loewiscreate