On Thu, Jul 2, 2020, 6:30 AM Greg Ewing <greg.ewing@canterbury.ac.nz> wrote:
On 2/07/20 8:04 pm, Serhiy Storchaka wrote:
> It has a problem with pickling (it is solvable).

Can you elaborate? The end result is a property object just the
same as you would get from using @property or calling property
directly. I don't see how it can have any pickling problems
beyond what properties already have.

> The larger problem is with using private (double underscored) variables
> and super().

I don't know what you're talking about here. I didn't use any
double-underscore names in my example.

I think what he may have meant is that if you tried accessing a double-underscore property of the outer class from the get/set methods, it won't properly de-mangle.

Similarly, if you wanted to overwrite a property by using this property approach in the sub-class, but also call super for the parent's class property getter from within the get/set this wouldn't work!?