Gregor Horvath <[EMAIL PROTECTED]> writes: > No, but the assumption here is that the maintainer / designer of a > class alaways knows everything and things are static. Unfortunatly > this is wrong in real live.
I'd say it's pretty far removed from how multi-person software projects actually work. > When you use a _ variable in python you know that this may break in > the future because of changing interfaces. Thats a typical engineering > Trade Off on my side. > One that is in other languages not even possible. A clear disadvantage. > Python gives me power and does not take it away like the others. Huh? If my car has a "feature" that lets someone blow it to smithereens from hundreds of miles away without even intending to, that's somehow an advantage? > The engineering decisions regarding my application should be on my > side, not the language lawyers. No problem, but any decision like that should be expressed in "writing", by re-declaring the variable so it's no longer private. -- http://mail.python.org/mailman/listinfo/python-list