On Jun 7, 2006, at 3:54 AM, Simon Willison wrote:
> > > On 7 Jun 2006, at 05:33, Joseph Kocherhans wrote: > >> 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. > > You can also use the ./manage.py --settings=myproject.testsettings > command-line flag if you don't want to mess around with your > environment variables. That did exactly what I was looking for. Now I just have to figure out the most efficient way to pre-populate everything. I'm thinking I'll have a 'test' app that has hooks for sticking in data that I can call before I run tests. Thanks everybody! Todd --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
