In light of the new expressions API, the idea of deprecating QuerySet.extra() has been informally discussed in IRC and elsewhere. I wonder if there is consensus to mark extra() as "unmaintained" and to suggest filing feature requests for functionality that can be performed through extra() but not through other existing QuerySet methods? There are at least several tickets (examples below) of edge cases that don't work with extra(). It seems like a waste of time to leave these tickets as accepted and to triage new issues with extra() if they won't be fixed.
https://code.djangoproject.com/ticket/24142 https://code.djangoproject.com/ticket/19434 https://code.djangoproject.com/ticket/12890 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6e1be326-3b17-49ca-accf-03eec5ad41ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
