Every setting in the current ini config files _could_ be very similarly presented in a py equiv, with the extra oomph that just about any transforms on nearly every part of the config system would also be possible. I can't think of any compelling reason to have static ini files. Marginal simplicity perhaps ?
>From my ex-PHP-centric point of view... my main PHP system allows me to put a simple index.php containing a single include line that pulls in a fairly small front controller that then pulls up a complete CMS. I can drop this one liner into any web aware folder and it starts up with decent set of introspective defaults and auto creates db/tables and, again, populates them with simple default values. There is zero setup or pre-configuration needed to get from 1 to infinity-1 different instances running off a single codebase on the same physical server... zero. Just plonk one-liner index.php in web folder, surf to (sub)domain, log in as admin, *then* configure for this particular site. What config files ? --markc
