On Mon, Mar 2, 2009 at 12:55 PM, Shai Berger <[email protected]> wrote: > > Hi Django developers, [...] > ...[T]he main objection to this feature is that it lets apps include their own > settings in the global settings object, and I tend to agree with that > sentiment. However, I still think it is much nicer for the application > settings to be concentrated in one place. This would help not only deployers, > but also developers who will be able to rely on IDE services (intellisense, > refactoring) for their own settings. > > My idea for not messing with the global settings object, is for each app to > have its own settings object, which serves as a proxy to the global settings > object. The global settings object remains un-tainted. With the appsettings > module [http://code.djangoproject.com/attachment/ticket/1371/appsettings.py], > the application would include a conf.py file looking like so: [...]
+1 Good work Shai! This is useful whether it gets into trunk or not, hope to read some committer's opinions soon tho :) -- Gonzalo Saavedra <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
