On Friday 17 February 2006 16:40, pbx wrote: > That got me thinking: How about annotating the default settings file > to describe all available settings? I'm talking about something along > the lines of Apache's default httpd.conf. <snip> > So, reasonable people, what do you think?
One of the problems with an annotated conf file is what happens at upgrade time, when new config options have been added to the system. In the case of httpd.conf, it's not too bad for me because dconf (Debian conf system) is great and asks me what to do (i.e. doesn't overwrite my updated version etc, and even shows me the differences between the two). But that obviously isn't the case for everyone, and certainly isn't feasible at all for Django. This means that you'll still have to go and read the docs for full information, and your fully annotated version is no longer fully annotated. Even worse are the cases where a setting is deprecated, or subtleties about its meaning are changed, but you might go on blindly believing what you read in your ageing settings.py Luke -- "Mistakes: It could be that the purpose of your life is only to serve as a warning to others." (despair.com) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
