On Mon, Nov 3, 2008 at 7:01 PM, pk <[EMAIL PROTECTED]> wrote:
> James is right that for any of my own app, I can just tell the user
> to put in some settings in the project level settings.py file. In fact
> that is exactly what I do now.
And that is what quite a number of popular third-party Djan
To clarify the question a bit more, I am talking about an "app" in the
sense of a reusable component that is developed by me but want
to distribute for others to use.
James is right that for any of my own app, I can just tell the user
to put in some settings in the project level settings.py file.
On Fri, Oct 31, 2008 at 8:29 PM, pk <[EMAIL PROTECTED]> wrote:
> 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?
If yo
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
pr
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 som
5 matches
Mail list logo
