I find that each app having it's own settings makes the app more
portable and opens up new possibilities, for example loading apps at
runtime which should be theoretically possible but I guess it's hard
to achieve and this point in time.
Erik
On 15.09.2008, at 12:31, Thomas Guettler wrote:
IMHO installing a new app should require user intervention. I don't
want to see new apps magically popping out and I don't want to
dynamically load anyone else's settings.py. I love the code I get from
pluggable apps but I prefer to keep settings.py for myself...
Why not have a manage.py *installa
On Sep 6, 5:58 pm, HenrikV <[EMAIL PROTECTED]> wrote:
> I would like to make Django support settings defaults for
> applications. Ideally defaults would be loaded together with
> global_settings, but of course that is impossible as INSTALLED_APPS
> must first be configured. So my approach is to
Thomas Guettler wrote:
> HenrikV schrieb:
>> I would like to make Django support settings defaults for
>> applications. Ideally defaults would be loaded together with
>> global_settings, but of course that is impossible as INSTALLED_APPS
>> must first be configured. So my approach is to add a defa
HenrikV schrieb:
> I would like to make Django support settings defaults for
> applications. Ideally defaults would be loaded together with
> global_settings, but of course that is impossible as INSTALLED_APPS
> must first be configured. So my approach is to add a default setting
> if settings doe
I would like to make Django support settings defaults for
applications. Ideally defaults would be loaded together with
global_settings, but of course that is impossible as INSTALLED_APPS
must first be configured. So my approach is to add a default setting
if settings doesn't already have the attri
