Comments on: Splitting up Django models

By: Sebastien

Sebastien — Thu, 29 Apr 2010 11:15:51 +0000

Hi !
I did what you said (thanks by the way, because it was -until recently- very useful!), but when I try to dynamically import some models, I got something strange…
Take a look a my code (which is in myapp.logger.__init__.py) :
from django.conf import settings

for log_hook in settings.LOG_HOOKS : try : __import__(log_hook) except ImportError as e : pass #from myapp.logger.hooks.vmm import *

Now, the problem is that when I try to import dynamically, I got some import errors, while if I directly write exactly the same import statement as the one generated, everything goes well…

Any idea to make this dynamic import work would be greatly welcome !!!

By: Thomas Holloway

Thomas Holloway — Thu, 08 Apr 2010 02:50:09 +0000

I couldn’t get it to work until I revised my __init__.py to simply:

from foo import Foo from bar import Bar

This works and makes sense since you don’t need to specify the full namespace from the top level.

By: Daniel Quinn

Daniel Quinn — Tue, 19 Jan 2010 01:20:47 +0000

This is one of those things that should really be part of the official documentation. I really wish that I’d found this 3hours ago rather than tinkering and surfing for all that time :-(

Great post though btw.

By: Ezequiel Bertti

Ezequiel Bertti — Sat, 12 Dec 2009 22:56:03 +0000

This is the best “HOW TO” to make split models file in django!!! thanks!!!

By: Nizam

Nizam — Tue, 01 Dec 2009 17:10:56 +0000

Yup, you are absolutely right. I have added a note at the end:

NOTE: One thing to note about ForeignKey relationships is that the import order in __init__.py is very important. Since Bar has a ForeignKey to Foo, Foo must be imported before Bar.

By: Dumb F

Dumb F — Tue, 01 Dec 2009 15:27:53 +0000

Thanks a lot for taking note of my earlier comment.

In the article where it says “You’ll also need to explicitly import each model class in the model module’s __init__.py file”, am I right in saying that the models would need to be imported in the proper order for syncdb etc to work right?

By: Nizam

Nizam — Sun, 29 Nov 2009 16:18:04 +0000

Sure thing. I just added that in as part of the example. Thanks.

By: Dumb F

Dumb F — Sun, 29 Nov 2009 13:42:37 +0000

N00b here. Could you make one of your models have a foreign key to the other one? That would make a more complete guide for us n00bs.

Thanks.

By: Nizam

Nizam — Fri, 27 Nov 2009 03:06:56 +0000

Pedro,

Thanks for your comment. All this time, I was putting my fixtures under the /models sub-directory. I thought it was a Django feature and it turns out to be a bug. :)

By: Pedro Costa

Pedro Costa — Thu, 26 Nov 2009 22:23:08 +0000

This would be great but has problems with fixtures:

http://code.djangoproject.com/ticket/6961

I saw here: http://justinlilly.com/blog/2009/oct/27/fix-your-models-subdir/
how to solve this problem and it works!!