#23046: Filtered GenericForeignKeys implementation -------------------------------------+------------------------------------- Reporter: mpasternak | Owner: nobody Type: New feature | Status: closed Component: Database layer | Version: master (models, ORM) | Resolution: wontfix Severity: Normal | Triage Stage: Keywords: | Unreviewed Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by timo):
* status: new => closed * needs_better_patch: => 0 * resolution: => wontfix * needs_tests: => 0 * needs_docs: => 0 Comment: As you said, perhaps someday. Generally it takes some time for things like this to mature and become de facto standards for common patterns. I'm going to close this ticket for now as it seems a bit premature. If you are interested in contributing to Django development, you may find the [https://docs.djangoproject.com/en/dev/internals/mailing-lists /#django-core-mentorship django-core-mentorship] list of interest. Thanks! -- Ticket URL: <https://code.djangoproject.com/ticket/23046#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.0714cb248e1f5725056c4133d5bdc725%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.