You should always consider that circular imports may indicate problems with how you structured your applications and/or models, however, if you're left with no choice, you can have an import statement inside a function, which generally solves most of these issues. Enviado desde mi BlackBerry de Movistar (http://www.movistar.com.ar)
-----Original Message----- From: bubu...@gmail.com Sender: django-users@googlegroups.com Date: Thu, 11 Apr 2013 11:08:26 To: <django-users@googlegroups.com> Reply-To: django-users@googlegroups.com Subject: Circular import problem Hi all, I have a util file, which will do some stuffs and then, update a model (so i have to import the models in this file). Also, in my models file, I trigger a post_save signal to call the util file file (so I have to import this file in the models file). Obviously, I will get a circle import problem. Therefore, what is the best practices in this situation ? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
