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

Mike Meyer mwm at mired.org
Thu Sep 29 00:40:06 CEST 2005

Paul Rubin <http://phr.cx@NOSPAM.invalid> writes:
> Mike Meyer <mwm at mired.org> writes:
>> Note that the quoted article only applies to *writing* attributes. It
>> doesn't say anything about needing accessors to *read* a
>> variable. This encourages me that the convention I use - adopted from
>> Eiffel, where the compiler enforces it - of freeling reading
>> attributes, but providing methods to write them - is a right way todo
>> things.
> Generally that sounds reasonable.  Obviously there are other examples
> when (e.g. for security) you have to make sure that variables can't be
> read by other classes, e.g. you have a class that stores a capability
> (or a password) in an instance variable, and uses it for privileged
> operations.  

If you can't trust the code that shares your address space, you're in
a world of hurt for security. Compile-time restrictions don't matter
for squat - you need serious restrictions on what the program can do
at runtime.

Mike Meyer <mwm at mired.org>			http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

More information about the Python-list mailing list