id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
28466	Clarify the definition of a lazy relationship in the docs	Malik A. Rumi	nobody	"The language of this page in the docs: https://docs.djangoproject.com/en/dev/ref/models/fields/#lazy-relationships has apparently been unchanged for 8 years, https://github.com/django/django/commit/6c36d4c4f8379433cdce150a64dad6a1f16097cd  so maybe I am the only one with this issue, but I draw your attention to the fact that the portion of this page in the docs where the link is anchored says NOTHING about lazy relationships. That term does appear, twice, but much further down, in fact, under two different headings. It is not at all obvious to anyone who doesn't already know what a lazy relationship is, that that is what is being defined when we are told to put quotes around foreign key references. Then, much later, in talking about many to one and one to one, we are told that these are handled like lazy - but when were we ever talking about lazy? We weren't! The only reason I 'got it' was because I found an answer on SO (actually two, to the same question) https://stackoverflow.com/questions/5680414/django-import-error-from-foreign-key-in-another-application-model  that explicitly calls this a lazy relationship. How else would anyone know? I don't think they would. I didn't. 

Fortunately, I think there is an easy fix. Just change this language from the docs by inserting the bolded text:

This sort of reference**, called a lazy relationship,**  can be useful when resolving circular import dependencies between two applications.

"	Cleanup/optimization	closed	Documentation	1.11	Normal	fixed			Ready for checkin	1	0	0	0	1	1