On Tue, Jun 06, 2006 at 10:33:42PM -0600, Joseph Kocherhans wrote:
>
> On 6/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> >
> > Does anyone know of a way to get all attributes of a module into
> > another module while overriding just a few?
>
> I think you want tocreate something like testsettings.py, and in that
> file do something like:
>
> from myproject.settings import *
>
> then override the specific settings you want. It won't work with
> manage.py, but your tests should be able to just set the
> DJANGO_SETTINGS_MODULE env variable to use the myproject.testsettings
> module.
I'd do it the other way round, leave the settings module to be the main
settings, then do something like:
try:
from myproject.localsettings import <LIST_OF_DATABASE_SETTINGS>
except:
<DEFAULT_DATABASE_SETTINGS>
Then just create a localsettings.db on the live and dev instances that
have the right settings in. I'm currently using this style setup for a
project, seems to work quite well, even using sqlite3 on the dev server
and postgres on the live server.
Cheers,
--
Brett Parker
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
