I figured out the problem. I had missed adding the top-level module to one of my
import settings lines. The problem was that even with the debugging output, the actual problem line never showed up in the exception trace. I actually found it by using django-admin.py shell and then importing one of the views modules that was giving me grief. Bingo, the evil import statement appeared. On Fri, 2007-06-15 at 09:33 -0400, Todd O'Bryan wrote: > Hey all, > > I'm trying to deploy a project I've been developing for a long time and, > in preparation, have tried to move everything (including settings.py, > etc.) into one overarching module. So, here's my setup: > [snip] > django-admin.py validate --pythonpath=/home/tobryan1/workspace/dmi/src/ > --settings=dmi.settings > > I get > > dmi.orgs: No module named settings > dmi.recommendations: No module named settings > dmi.shared: No module named settings > dmi.calendar: No module named settings > dmi.assignments: No module named settings > 5 errors found. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
