During the refactor of lazy operations abstract models stopped resolving
their related field model reference by themselves in order to prevent
pending lookup pollution. This was necessary in order to warn the users about
unresolved relationships in a reliable way.
This change introduced a subtle regression when an abstract model with a
lazy app relative (missing an app_label suffix) relationship is derived as
a concrete model in another application:
refered = models.ForeignKey('Refered')
abtract = True
from app1.models import AbstractReferent
Now that relationships defined on abstract models are only resolved on
definition of concrete subclasses the `app2.Referent.refered` points to
`app2.Refered` when it used to point to `app1.Refered`.
Here are the solutions I had in mind:
1) Refuse the temptation to guess; raise an exception on `app2.Referent`
definition about the ambigous relationship and point to resolution options.
2) As abstract models should really just be considered "placeholders for fields"
consider this new behavior the correct one. This could be considered a new
feature and a deprecation path would have to be thought of.
3) Revert to the previous behavior by converting app relative lazy relationships
to the "app_label.Model" form on `RelatedField.contribute_to_class`.
I'd favor the first option over the others because I feel like this is really
an edge case where both behaviors have merit (and a bad pratice i'd like to
prevent) but the third one is definitely the safest option.
Thanks for your feedback,