On Mar 10, 2010, at 3:21 AM, Joan Miller wrote: > Whatever configuration system using variables of a language is a > disaster and it's going not maintainable as has been showed in Django.
I strongly disagree. It may not have worked *for you*, but there are a metric ton of projects out there using Django that get along just fine. > > My solution was to use YAML, and then to use a class to convert it to > Python. Features: > > * The python configuration is only re-built if yaml config. has been > changed. > * It can add some configuration depending of some variable, as debug. > See in lines where is '?'. > * It adds the absolute paths where it's necessary. > > - YAML config. initial => http://pastebin.com/CVqGD1eL > - Python generated => http://pastebin.com/AB4FaBgy I'm not sold on using something like YAML to convert into Python. I want Pinax to be as much like Django as possible. This is would take in the opposite direction even if it is generating the Python. The problem we are addressing is not configuration format, but rather loading order and scope. Your solution doesn't give us anything to solve the problems we are after. Brian Rosner http://oebfare.com http://twitter.com/brosner -- You received this message because you are subscribed to the Google Groups "Pinax Core Development" 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/pinax-core-dev?hl=en.
