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 loewis, schuppenies
Date 2008-09-14.16:23:01
SpamBayes Score 1.318018e-09
Marked as misclassified No
Message-id <48CD3A63.8040109@v.loewis.de>
In-reply-to <1221387146.31.0.0417653564604.issue3690@psf.upfronthosting.co.za>
Content
>> In any case, I also think this doesn't matter much either way. 
> Why do you think so?

What's the actual difference that this change makes? At most 8
bytes per object, right? And for two objects in total. So if somebody
would compute memory consumption, they might be off by not more
than 14 bytes, in total. Compared to all the other errors that memory
computation makes (e.g. malloc headers, rounding-up to multiples of
8 in obmalloc) which aren't accounted-for in sys.getsizeof, this
difference is negligible.

What's more, the small_ints aren't dynamically allocated, either,
but instead, each small_int takes a complete PyLongObject. If
that was also considered in long_sizeof, the computation would happen
to be completely correct for bool also.
History
Date User Action Args
2008-09-14 16:23:02loewissetrecipients: + loewis, schuppenies
2008-09-14 16:23:01loewislinkissue3690 messages
2008-09-14 16:23:01loewiscreate