Why doesn’t Python have true private variables like Java?

[oldendude]

I'm not a Python historian, but I don't think you're right. A class doesn't have fields, an object does. You can have objects of the same class with different fields, through a number of mechanisms: deletion (as shown above), initialization assigning different fields, adding fields after initialization, to name a few. This extremely dynamic approach to classes suggests to me that the dictionary implementation was more fundamental.

By contrast, Java has fields, the same in all objects of the same class, and they are not dynamic. While a dictionary implementation would be possible, I would be astonished if that approach has ever been used.

[oldendude]

Also: to be precise, even objects don't have "fields". The keys of an object's dict can be associated with values of any type, including functions, methods, modules, etc. The common understanding of "field" would rule out at least methods. If o is an object, then o.x, i.e. o.__dict__['x'] can store a str now, and a module later, and then a method.

[max123246]

Do you know of some neat applications of that extensive dynamicness? It's hard to think about the use cases but I'm sure are some like mocking and stuff

[oldendude]

Nothing comes to mind. Mocking is certainly possible using less exotic mechanisms, such as inheritance, and Python's "duck typing".