> The big boat-anchor feature of Python is "setattr", combined with the ability to examine and change most of the program and its objects. [...] If "setattr" we

> The big boat-anchor feature of Python is "setattr", combined with the ability to examine and change most of the program and its objects. [...] If "setattr" were limited to a class of objects derived from a "dynamic object" class, most of the real use cases [...] would still work, while the rest of the code could be compiled with hard offsets for object fields. Isn't __slots__ made for that specific usecase? (when you want to optimize your code by specifiying specific attribute names) I think the "dynamic" behavior is a sane default (since most people don't need that optimization).