I am getting this error under either mod_python or mod_wsgi, when the
project functions just fine under the development server. I've pasted the
more detailed traceback here <http://dpaste.org/wqZw/> (edited out some of
the sensitive corporate stuff). We are using Django 1.0.2 and Python 2.6 on
Ubuntu Jaunty.
Until recently, we've had our code contained within one massive application
(which was fine at the start, but has since grown huge and unwieldy) so we
decided to split our code into multiple applications that depend upon each
other. In our current codebase, models from some apps will have ForeignKeys
to models in other apps. For example, the employees application relies
heavily upon the companies application, and vice versa. Due to circular
import issues, we've had to use the lazy model resolution feature (where the
string name for a model is used instead of the model class itself) to refer
to the models from other applications. (eg,
models.ForeignKey("appname.ModelClass"))
All of this works out just fine under the development server, both with
debug on and off; but when we attempt to redeploy the site under apache, the
traceback linked above appears in the logs, and the site is non-functional.
Ticket #10405 <http://code.djangoproject.com/ticket/10405> (which looks as
if it's been delegated to 1.2) seems to deal with this issue, with two
suggestions for working around the bug, but mkibbel's
suggestion<http://code.djangoproject.com/ticket/10405#comment:11>doesn't
work for us, and I need some clarification about Jacob's
suggestion <http://code.djangoproject.com/ticket/10405#comment:10>.
Jacob suggests to "make sure you define ModelForms after Models", but this
seems to be pretty much how I've already set things up. My forms are not
defined alongside my models (they are separated into forms.py and
models.py), and since my models refer to models in other applications, how
can I ensure that the forms in one application are not interpreted before
the models from another application? I'm assuming that this has to do with
the import order when the applications are initially imported by Django, but
how can I control that? Am I missing something obvious here?
Any other ideas from the crowd would be welcome, as this is currently a
show-stopper for us (since we can't even deploy our site at the moment). We
can always roll back to having one gigantic behemoth application, but we'd
obviously prefer not to, if this can be resolved with any efficiency.
Thanks to all for any input.
--
Visit me @ http://killarny.org
Sent from Provo, UT, United States
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
