> if youre trying to lock down __dict__ and all that with magic, i > think you need to instead get better users :). its python, its > unrealistic to try to make a java-sandboxlike application that cant > be messed with. stop with this java labeling. think wider. java is just some (poor) language that does not allow dynamic properties. For certain usages static properties are good. For some - extremely good (protocols). For other usages they are bad, and just out of question.
Language and its characterisitcs (dynamic/static typing, dynamic/static containnment, declaration vs definition, scopes, visibility, callability, expressions, etc) are just tools. So instead of using 20 poorly combinable/tweakable readymade languages, i simulate - or express their semantics - all of them within python, within same application or even library. Python allows me to do that (eh, some magic IS required). And when i neet yet another semantix (e.g. makefile-like functionalism, or .ini file configs, or report-description language, whatever), i just go ahead and express it in python syntax, sometimes replaceing the whole semantix underneath, e.g. what class namespace is. Thus i save on readability, the parser is ready, the result is python-objects which are diredctly application usable, etc. As of the users - this is called defensive programing. somewhat Like defensive driving. The user might be me, 1 month later, using adress instead of address and losing 2 hours to find out why that stupid thing broke. ciao svil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
