Well, after looking at this thread [1], it would appear that the problem came down to a recursive imports. I had two apps referencing each others models, with m2m references going back and forward, which created a whole mess when it came to validating.
So, since this was down to bad design on my part, I've revisited the structure of the models involved, and the final outcome is a much more elegant and intuitive application. [1] http://groups.google.co.uk/group/django-users/browse_thread/thread/c9f6e581cf03057d?tvc=2&q=django+validate+cannot+import&hl=en On 26/01/07, Phil Powell <[EMAIL PROTECTED]> wrote: > This is a very odd one: > > I have a number of apps installed, and I'm updating models.py in one > of them to import the models of another, like this: > > from mysite.myapp1.models import MyModel > > Nothing unusual about that, huh? Except now if I run manage.py > validate, I get errors like this: > > mysite.myapp2: cannot import name MyModel > mysite.myapp3: cannot import name MyModel > mysite.myapp4: cannot import name AnotherModel > > I remove that import line, and all is fine. I've checked that all > apps are installed in settings.py, although changing the order of > those installed apps gives me slightly different apps complaining > about different models. > > Very weird. Has anyone experienced anything similar? > > -Phil > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
