YAML IS AWESOME. As a configuration language, It is fast, flexible, metaprogrammable.
jbrooksuk wrote:To change it now would be a big change.
It would NOT be a big change, In-Fact it would be a dropin replacement because JSON is a valid subset of YAML.
All current JSON config files would work perfectly when being parsed by the YAML, making this the perfect time to switch over.
People won't even have to know that PyYaml is actually parsing their Json file.
In additon to this, YAML has some really cool features such as anchors which allow us to reduce repetition in config files (define once, use many times.)
From the wiki definition:
YAML syntax was designed to be easily mapped to data types common to most high-level languages: list, associative array, and scalar. Its familiar indented outline and lean appearance make it especially suited for tasks where humans are likely to view or edit data structures, such as configuration files, dumping during debugging, and document headers (e.g. the headers found on most e-mails are very close to YAML). Although well-suited for hierarchical data representation, it also has a compact syntax for relational data as well. Its line and whitespace delimiters make it friendly to ad hoc grep/Python/Perl/Ruby operations. A major part of its accessibility comes from eschewing the use of enclosures like quotation marks, brackets, braces, and open/close-tags which can be hard for the human eye to balance in nested hierarchies.
So please, reconsider YAML. It's awesome, It's powerful, It's a drop-in replacement.