Re: Problem Django.19 upgrade and circular imports

So I've tried going back to Django 1.7 but changing the app configuration to use the AppConfig class and I've hit upon the same issue. It would seem that part of the key is the fact that when the system hits this line: /home/osinski/Projects/feastly/apps/account/models.py in () 11 12

Re: Problem Django.19 upgrade and circular imports

The thing is that in my case, I have a model in the 'accounts' app which inherits from a model in 'common', therefore I need the import to happen in one's models. I've tried this in Django 1.8 and I see the same behavior; therefore the change occurs between the latest versions of 1.7 and 1.8.

Re: Problem Django.19 upgrade and circular imports

On Thu, Mar 3, 2016 at 3:28 PM, Andres Osinski wrote: > Hi everyone! I'm having an issue with circular imports in Django 1.9 that > I have not seen in my app, which had been running 1.7 before. > > I have a Django app in apps.common, which has its associated >

Re: Problem Django.19 upgrade and circular imports

No ideas off the top of my head. You could try bisecting to find the commit in Django where the behavior changed. https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression On Thursday, March 3, 2016 at 6:29:38 PM UTC-5, Andres Osinski wrote: > > Hi

Problem Django.19 upgrade and circular imports

Hi everyone! I'm having an issue with circular imports in Django 1.9 that I have not seen in my app, which had been running 1.7 before. I have a Django app in apps.common, which has its associated apps.common.models too. No imports on __init__.py or anything of the sort. When I my app in