Whatever configuration system using variables of a language is a disaster and it's going not maintainable as has been showed in Django.
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 On 26 feb, 07:11, Jared Forsyth <ja...@jaredforsyth.com> wrote: > I have been looking around for a way of managing user-configurable > application settings, and the only solution I have found is dbsettings, > which looks like it hasn't been touched in 3 years. > So, I would like to know: is dbsettings dead? Or is there a different > generally accepted method for having user-friendly app settings? (e.g. don't > require code modification) > > I think that this idea is pretty essential to django's ease of use; there > are many applications which have (or should have) settings which only effect > UI or minor behavioral issues, and shouldn't require a server restart to > effect (and imo shouldn't require server write access). It seems that the > most viable solution would be to have a database managed settings system (in > the form of a .contrib module) which would manage this. It also seems that > having such an infrastructure in place would really encourage app > maintainers to have more settings, thereby making the apps even more > portable. > > Any thoughts? > > Thanks, > Jared -- 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.
