Will python never intend to support private, protected and public?
mwm at mired.org
Mon Oct 3 06:31:33 CEST 2005
Paul Rubin <http://phr.cx@NOSPAM.invalid> writes:
> Mike Meyer <mwm at mired.org> writes:
>> >> Compile-time restrictions don't matter for squat - you need
>> >> serious restrictions on what the program can do at runtime.
>> > You need both.
>> Yup. Any language besides Java even *try* to provide both for a
>> production environment?
> Yes. Python tried. It had a module called rexec for that purpose.
> I keep mentioning that, and you keep ignoring it. Rexec was around
> for a long time, and was removed for technical reasons with some
> reluctance. There is nothing un-Pythonic about the idea.
If you've mentioned it before, it wasn't to me. Or maybe my news
server dropped it.
Rexec was removed because it didn't work. Just like bastion and every
other attempt to create a "safe" environment in Python. Any security
wonk worth his pay will tell you that you don't add security to
something after the fact if you want good security. You design it in
from the beginning.
Of course, what rexec tried to do and what "private" do are orthogonal
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