I think you're finding out that there are many different approaches to
reusable app configuration, but all have their trade-offs.
I think there is also some middle ground between always checking for the
value and loading it initially, and that's to be able to reload. In your
app's settings fil
Thanks very much and, yes, that code is what I've found. In your personal
opinion, would you use a setup like that (
http://passingcuriosity.com/2010/default-settings-for-django-applications/)
for default settings? or is it a little bit over the top for small apps?
I think I'll try my approach for
The only thing I've seen which handles all the cases you mention
is http://passingcuriosity.com/2010/default-settings-for-django-applications/
. That may also be what you were referring to about seeing something on
github.
As to your new question, I think that would work, because every time y
No, you're not, but, there isn't a way to load or inject the app settings
so that diffsettings and other project level things (like testing) can see
them? That's my question. I've read something on a github repo but it seems
clunky and over-done. My main goal really is to change some settings on th
This approach is only useful for modules that import app.settings and use
things that it defines. It doesn't affect things that import settings from
django.conf .
Your app can import settings from app, and get your settings. That's not
going to affect any other app. If you want to affect what o
Hi, I'm having troubles using the override_settings decorator. The thing is
I'm writing an app that has it's own settings and I'm doing it with the
approach of putting a settings.py file on the app folder with something
like this:
from django.conf import settings
from django.core.exceptions imp
6 matches
Mail list logo