1) In implementation, how is a YAML configuration file any different than the Java/XML example that you offered? Syntactical differences between XML and YAML aside, both systems define settings in markup languages (which by definition have minimal capability for logic) that are eventually parsed (by potentially faulty parses) into programming language datatypes.
2) The beauty of a programming language configuration system like Django's is that it gives developers the option and ability to refactor settings systems in ways that make sense to them and their projects. For example, it provides you with the flexibility to keep settings in a YAML file, if you so choose. My use case is a bit unique: I wanted environment-specific (e.g. dev, staging, production) settings overrides, kept in source-controlled files unless they were of sensitive nature (DATABASE_PASSWORD, SECRET_KEY, etc). Python's flexibility gave me the ability to turn settings into a full-blown module, with magic-keyworded imports based on the machine's hostname and path of the settings module. This flexibility is not by accident. On Wed, Mar 10, 2010 at 8:16 AM, Joan Miller <pelok...@gmail.com> wrote: > It's a disaster from the maintenance view point. If it were not so, > then people would not be proposing to refactor the settings as has > been made in Pinax, or from multiple posts so many times. > > This is nothing new. Many people dislikes that kind of configuration, > of the same that many people hates java by its fu**ing XML config. > files. > > On 10 mar, 13:49, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > > On Wed, Mar 10, 2010 at 6:18 PM, Joan Miller <pelok...@gmail.com> wrote: > > > Whatever configuration system using variables of a language is a > > > disaster and it's going not maintainable as has been showed in Django. > > > > That's a pretty wild assertion to make without any evidence, and it's > > completely contrary to my personal experience. Care to back it up? In > > what way has Django demonstrated that using a programming language for > > configuration files is a disaster? > > > > Yours, > > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
