I was trying some things out and this seemed to work:
Put "import app1.settings. as APP1" in settings.py. Then you can use
settings from app1 like this:
from django.conf import settings
settings.APP1.set1
I think the import has to be capitolized or else it never even shows up when
you try to retrieve the setting. I'm curious about how the settings file
works now, I'll do some more reading about it soon.
--Michael Brown
On Tue, Apr 27, 2010 at 9:50 AM, Eric D Helms <eric.d.helms(a)gmail.com>wrote:
This is to follow-up on how to handle settings.py in an application
specific way. Generally speaking - the Django community does not feel that
the this issue requires a single encouraged solution. The feeling is that
different situations and deployments call for different needs and thus it
should be up to the developer to decide.
The link below is from the Django wiki, and enumerates ideas and concepts
for splitting up the settings file.
http://code.djangoproject.com/wiki/SplitSettings
I feel we should review and decide what idea will work best for us and
enforce it as part of our own development procedure.
- Eric Helms
_______________________________________________
Opus-devel mailing list
Opus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/opus-devel