>>45
Yes. Don't documentate what the "lol" property if you don't want them to touch it, or tell them what it does if you must or want for some reason and add "don't touch lol alright?". Other modules shouldn't mess with it, and if they do, it's their fault, not yours.
You can mangle these properties if you feel better, but if you get really CIA-conspiration-paranoid you won't be happy that there'll always be a way to mess with other objects, even if that implies using __dict__. Could Guido add forced private properties to objects? Probably, but what's the big deal? You can still live with how it is now. The fact you CAN mess it up doesn't mean you WILL mess it up. And in a reflexive language, chances are that you'd always be able to access any part of an object somehow.