On 14/01/21 11:49 am, Cameron Simpson wrote:
The "pure" OOP approach, where method calls are used as messages to set
or fetch aspects of the object, is usually does with getter and setter
methods like:
x = o.getX()
o.setX(9)
People use get and set methods, not because it's somehow
On 13Jan2021 10:37, songbird wrote:
> my momentary conceptual problem is that to me OOP means
>being able to encapsulate data structures and code from
>other parts of the program, but to me it doesn't look like
>that is how python is designed. this is probably a complete
>aside to this whole
Chris Angelico wrote:
...projects that fade...
> That's not really something Python can ever control, but I can say
> with some confidence that the big libraries like Qt and GTK are going
> to adapt, one way or another. And perhaps more importantly: Neither
> input()/print() nor web applications
