I think my earlier link to wiki discussed how properties can be simulated in C++.
I'm still wondering whether PySide has not made a design error in their QPoint implementation. Its more Pythonic to make data attributes public (the philosophy is, let the programmer do what they want, even if they get in trouble) without hiding them behind getter/setters. If the developers of PySide later need to intercede, they can use properties to make it still look like a data attribute, but use their defined getter/setter doing whatever intercession they need. But its possible that what the PySide developers can do is constrained.
Re: "Qt’s design principles to (NOT) expose otherwise private implementation details as public attributes". In C++? Do those principles necessarily carry over to PySide?
After all, a point IS data, two numbers usually called x and y. In other words, that seems to be a rather fundamental "property" of a point. Why obscure that with getter and setters?
I don't mean to complain too much, I really appreciate the beauty of Qt and PySide.