On 2/18/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > 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.
Personally, I like the idea of settings.py generating all the possible settings, but with all the 'not normally required' settings present (with documentation), but commented out. e.g., the generated settings.py file would contain sections like: # E-mail address that error messages come from. #SERVER_EMAIL = '[EMAIL PROTECTED]' This exposes all settings so that newcomers know what is available for configuration, shows the default value for those settings, demonstrates the expected format if the user does want to customize that setting. The settings that are currently exposed through settings.py remain uncommented, indicating that user input is probably required before the application is started for the first time. Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
