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 aliles, benjamin.peterson, hynek, jcea, loewis, pitrou, serhiy.storchaka, stutzbach
Date 2012-09-16.18:52:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347821529.0.0.219140270563.issue15490@psf.upfronthosting.co.za>
In-reply-to
Content
Well, I do think that it's not very important to make __sizeof__ strictly exact according to some specification. I'm also not sure we want to complicate maintenance when the calculation becomes tedious or difficult.

To me __sizeof__ is mostly an educational tool which gives a hint at the memory impact of an object, but cannot really convey a precise information except for trivial atomic types.
History
Date User Action Args
2012-09-16 18:52:09pitrousetrecipients: + pitrou, loewis, jcea, benjamin.peterson, stutzbach, aliles, hynek, serhiy.storchaka
2012-09-16 18:52:09pitrousetmessageid: <1347821529.0.0.219140270563.issue15490@psf.upfronthosting.co.za>
2012-09-16 18:52:08pitroulinkissue15490 messages
2012-09-16 18:52:08pitroucreate