Context Navigation

Changes between Version 2 and Version 3 of Ticket #24215, comment 5

v2	v3
3	3	Sorry about the delay, I didn't get an email notification of your comment. Thanks for replying.
4	4
5		I use it this in Mezzanine to [https://github.com/stephenmcd/mezzanine/blob/8e0ff285c9761642cc8544f59b583a75b7821fff/mezzanine/accounts/models.py wait on both a user model and a profile model] which are both string references. ~~It's more defensive ther~~e than it is strictly necessary, but it demonstrates the point. I leave more creative uses to future generations. :)
	5	I use it this in Mezzanine to [https://github.com/stephenmcd/mezzanine/blob/8e0ff285c9761642cc8544f59b583a75b7821fff/mezzanine/accounts/models.py wait on both a user model and a profile model] which are both string references. That usage is more defensive than it is strictly necessary, but it demonstrates the point. I leave more creative uses to future generations. :)
6	6
7	7	I hear you about `add_lazy_relation` being used outside of Django (I do it). If it is used a lot, I see that as a good reason to clean up and document the API, though with an extended deprecation timeline – pave the cowpaths. I've done a quick search on GitHub but [https://github.com/search?l=python&q=add_lazy_relation&type=Code&utf8=%E2%9C%93 most of the results are Django builds in other people's repos], so it's not all that helpful. Perhaps I should poll django-users to get a sense of how widely it's used?