Will python never intend to support private, protected and public?

Paul Rubin http
Wed Sep 28 14:01:13 CEST 2005


Simon Brunning <simon.brunning at gmail.com> writes:
> I thought about it, but I didn't mention it in the end because this
> feature ("name mangling") isn't intended as a mechanism for making
> things private - it's intended to prevent namespace clashes when doing
> multiple inheritance. It can be used to make things private, true, but
> that's abusing the feature, just as using __slots__ as a way of
> "declaring variables" is an abuse - (__slots__ is a memory
> optimisation feature).

Good explanation.



More information about the Python-list mailing list