I saw this discussion on python-dev as well... Unfortunately IronPython currently gets it wrong .
Dino Viehland | 07/06/23 - 5:03 pm | #

Hmmm... well, if the cost is making attribute access several times slower for IronPython then I am not necessarily bothered!
Fuzzyman | Homepage | 07/06/23 - 5:25 pm | #

You're not bothered by the same kind of slight incompabilies that make Javascript programming a hell?

It would be much better if IronPython used a cache instead of breaking protocols, if it actually makes any difference at all.
Simon | 07/06/23 - 7:58 pm | #

This is one of the many reasons why I like using descriptors and __slots__ together. You can make some very efficient python. Lazy evaluation descriptors can be quite powerful (get method does a bunch of work and caches result for future gets).

http://www.dougma.com/?p=31
Doug Napoleone | Homepage | 07/06/23 - 8:05 pm | #

Hey - do you know where the docs for the @property syntax is?
jesse | Homepage | 07/06/24 - 5:13 pm | #

Never mind, it just clicked in my head, @property is simply using decorator syntax to decorate the function with the builtin property method. I'm too used to the direct property(xxxx) calls
jesse | Homepage | 07/06/24 - 5:21 pm | #