+1 - Anssi
On Friday, July 31, 2015 at 11:00:01 PM UTC+3, Tim Graham wrote: > > I had in mind a documentation note like this: > > Use this method as a last resort > > > This is an old API that we aim to deprecate at some point in the future. > Use it only if you cannot express your query using other queryset methods. > If you do need to use it, please file a ticket with your use case so that > we can enhance the QuerySet API to allow removing extra(). We are no > longer improving or fixing bugs for this method. > > On Friday, July 31, 2015 at 2:07:34 PM UTC-4, Collin Anderson wrote: >> >> I wonder if there's a way in the docs we can deprecate it as in "we don't >> recommend you use it", but not actually schedule it for removal. >> >> On Friday, July 31, 2015 at 2:01:20 PM UTC-4, Marc Tamlyn wrote: >>> >>> I don't know about unmaintained, but I think there's a consensus that >>> .extra() has a horrible API and we should do away with it eventually. That >>> said I think there are still enough things that can't be done without it at >>> present. A lot fewer now we have expressions, but still some. >>> >>> I'd be happy to put a moratorium on improving it, but we can't deprecate >>> it yet. >>> >>> On 31 July 2015 at 18:58, Tim Graham <timog...@gmail.com> wrote: >>> >>>> 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-develop...@googlegroups.com. >>>> To post to this group, send email to django-d...@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 >>>> >>>> <https://groups.google.com/d/msgid/django-developers/6e1be326-3b17-49ca-accf-03eec5ad41ef%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- 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/3d1f957c-318b-4a28-8158-442f2e6cbb55%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.