> I have a mild preference for fixing the config files to be more
> directly legal Python.
>
> Thoughts?
+1. The first times I tried to modify the config files I had a hellish
time trying to understand how everything fit together. It isn't
entierly obvious how the path() function works or how foo.bar is valid
when in a real Python script you would get a NameError on foo since
foo hasn't been bound yet. When
foo.bar = "baz"
path("/static")
static_filter.on = True
is equivalent to:
{ "global" : { "foo.bar" : "baz" },
"/static" : { "static_filter.on" : True } }
I don't understand why anyone would use the "magic" first alternative
over the second one which is entierly readable and doesn't require
reading documentation to understand.
--
mvh Björn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
