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


Ignore:
Timestamp:
Feb 8, 2015, 9:47:52 PM (10 years ago)
Author:
Alex Hill

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24215, comment 5

    v1 v2  
    55I 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 there than it is strictly necessary, but it demonstrates the point. I leave more creative uses to future generations. :)
    66
    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. 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?
     7I 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?
    88
    99I propose:
Back to Top