On 6 jan, 19:45, Ben Eliott <ben.dja...@googlemail.com> wrote: > Not that pretty/efficient but you could use contenttype contrib > temporarily. > IF ClassB has a ForeignKey to Class A could you extract the Class A > model from a foreign key via Class B's .meta? > Or the Class B could have a callable method which returned the > instance of the model you want... > Not sure whether/how these will work but just throwing out some ideas. >
This looks to me like dirty hacks that only add accidental complexity instead of adressing the real problem. At least importing within a method is a simple, well-known and idiomatic solution to circular imports. The "correct" solution would be to turn models.py into a package, split its content in submodules (with class A and B in distinct submodules, each with their own manager), and use the package's __init__.py to expose the submodule's Model classes at the top-level, but IIRC this doesn't work well in Django (never had that problem FWIW, since I tend to split my projects into a lot of small apps). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
