Hi everyone, I submited a PR[1] that partially reverts the initial fix and document how app relative lazy relationships behave when defined on abstract models subclassed as concrete models in foreign applications.
Reviews welcome! Simon [1] https://github.com/django/django/pull/6178 Le mercredi 10 février 2016 16:29:52 UTC-5, charettes a écrit : > > I should have mentioned that this behavior is reproducible since at least > Django 1.6 and has not been introduced by Django 1.8. I wouldn't be > surprised > if it has always been working before the fix was introduced. > > Still, as you mentionned the conditions required to achieve this were > really > convoluted before the lazy operations refactor. > > Simon > > Le mercredi 10 février 2016 16:11:43 UTC-5, Shai Berger a écrit : >> >> On Tuesday 09 February 2016 23:33:50 charettes wrote: >> > Hi everyone, >> > >> > The chosen fix[1] unfortunately introduced a new regression[2]. >> > >> > It looks like the behavior described in the previous ticket was >> possible >> > with >> > Django 1.8 under certain circumstances[3] where the abstract models >> defined >> > in a foreign application were derived as concrete models in another >> > applications >> > before the abstract models relations are resolved (if they are ever >> > resolved): >> > >> >> The explanation is complex enough, the case where it works edgy enough, >> that >> I'd be content to call this a bug in 1.8. I'm pretty sure the specifics >> of this >> resolution are not documented, and my sense from reading the ticket is >> that if >> you'd try to document the behavior you'll reach the conclusion that it >> probably isn't intentional. >> >> My 2 cents, >> Shai. >> >> > >> > [1] >> https://github.com/django/django/commit/bc7d201bdbaeac14a49f51a9ef292d6 >> > [2] https://code.djangoproject.com/ticket/26186 >> > [3] https://code.djangoproject.com/ticket/26186#comment:8 >> > [4] https://code.djangoproject.com/ticket/24215 >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fa69a047-a210-4a7a-a62c-26298eef4005%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
