Re: Problems importing model classes that reference each other...

2011-05-15 Thread Leo
As Shawn said, if you really must have both apps refer to the other's models, then then they're not really separate apps. If you're just trying to resolve a generic circular-reference problem, remember that ForeignKey can also take the name of a class as its first argument, see

Re: Problems importing model classes that reference each other...

2011-05-14 Thread Shawn Milochik
If you have two models that need to explicitly refer to each other then they should probably be in the same app. If they need to be in two apps, you can have a foreign key in one and from the other use the RelatedManager to access the first. You'll have to make these decisions based upon

Problems importing model classes that reference each other...

2011-05-14 Thread Contoured Solutions
I am trying to create a simple billing/CRM app for my company. I have create a Django project with the following apps: sales_manager office_manager customer_manager Within, I have models representing things like Customers, Contacts, Projects, Tasks, etc. The problem I am having seems to arise