On 8/7/06, Kevin Menard <[EMAIL PROTECTED]> wrote: > I would be all for this. I never liked that the settings file > contains both project-wide and user settings. Since it's > project-wide, it gets added to the SCM. Since it contains user > settings, users really shouldn't commit it back. I realize it's > Python code and all that, but it seems to be a flaky default to me.
I'm not sure I understand the difference between "project-wide" and "user" settings -- would you be willing to clarify? Settings are settings, as far as I'm concerned, and if you're distributing a Django app, you shouldn't be bundling a settings.py file with it... Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
