On 2/17/06, pbx <[EMAIL PROTECTED]> 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.
Note that django/conf/global_settings.py holds the default values for every setting, and it's annotated. Of course, you don't edit that file, so the annotation is mainly for Django developers rather than Django users. The default settings.py file that's generated for "django-admin.py startproject" just contains the basic settings that most people will probably want to change. So the question is, do we give the generated settings.py file all the possible settings, or does it continue to have just the settings that are commonly changed? I really could go either way on this. Whatever we do, I like the idea Paul mentioned that we could generate an intelligent "diff" of the settings to find out which settings aren't default. Very cool! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
