I'm a little confused as to the purpose behind the question, it feels pretty general, so I have a few questions.
1. When you say application are you talking about django apps generated via the "manage.py startapp" command? 2. LazySettings allows for a "proxying" of the Global settings in your projectsname.settings. So I'm wondering if you're talking about in each "application" from (1.), that you'd have a "local" settings? 3. Refactoring for portability? as per my understanding "refactoring" means to rewrite better or to improve upon a code block/segment/file whatever, are you talking about the ability to copy paste an "app"(1.) into another django project created via django-admin.py so that it maintains it's own ability to have a local configuration that is universal regardless of what django project it sits in? On Fri, Oct 31, 2008 at 06:29:46PM -0700, pk wrote: > > There are always needs for application level configuration settings. I > really like the way settings.py works, with a package (django) level > default settings overridable by local settings. However looking at the > whole LazySettings setup it is not easily used outside of django/conf. > Am I missing something? Should that mechanism be refactored so that it > can be used for user applications? Is there a better way to do > application level configuration -- i.e. for app designed to be > distributed and reused? > > Thanks, > P.K. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
