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 josh.r
Recipients josh.r, lemburg, ncoghlan, pmoody, r.david.murray, rhettinger, sbromberger, serhiy.storchaka
Date 2014-12-24.00:05:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Marc-Andre: Oh, I know. I proselytize to coworkers on the virtues of using __slots__ for classes that will have many instances created (particularly since entirely too much of our stuff is still Py2.7, so we don't have the "free" savings from shared key dictionaries). Heck, I particularly enjoy inheriting from an inlined collections.namedtuple and an empty __slots__(which does add 8 bytes to the size over declaring the __slots__ directly, but gets you as close to truly immutable instances as you can get when you need them, not just "we're all adults here" immutable instances).

I'm just pointing out that if he thinks 56 bytes per object is too large, he's going to be disappointed with what Python has to offer. General purpose user-defined Python objects don't optimize for low memory usage, and even __slots__ only gets you so far.
Date User Action Args
2014-12-24 00:05:02josh.rsetrecipients: + josh.r, lemburg, rhettinger, ncoghlan, pmoody, r.david.murray, serhiy.storchaka, sbromberger
2014-12-24 00:05:02josh.rsetmessageid: <>
2014-12-24 00:05:02josh.rlinkissue23103 messages
2014-12-24 00:05:02josh.rcreate