On 08/08/06 02:46, Malcolm Tredinnick wrote: > On Mon, 2006-08-07 at 14:22 -0400, Kevin Menard wrote: >> On 8/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: >> >> > We don't need a default solution for this. It's not within the scope >> > of this project to tell people how they should organize their settings >> > files. Take that opportunity to showcase your individualism. >> >> With the lack of an endorsed convention, I expect to see this question >> to continue to come up. IMHO, this is a common enough scenario to >> warrant more than a simple write-off. > > Add your favourite ideas to > http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters and > see if they work for other people. > > Adrian's point is quite valid. Setting policy is something you do when > there are real benefits to it and few or no other options. In this case, > you have a full Turing-complete language available to do whatever meets > your needs and (important point) is has zero maintenance cost for the > developers (my favourite kind of flexibility). >
I've created a wiki page [1] with the different ideas from this thread and linked to it from the DosAndDonts page [2]. I hope that's ok for everybody who has posted their ideas/solutions here. Please add to that page if you have other ideas. Steven [1] http://code.djangoproject.com/wiki/SplitSettings [2] http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
