The 'con' side argument is that it would create in inconsistency in the API, since we don't have any other negated lookups either. If we can get the same behaviour by fixing the current API, Django should not introduce an unnecessary consistency. ("Closed as wontfix by core dev" is not an argument against the ticket, it is a simple rule that you must discuss such a ticket on the mailing list before reopening it.)
Anyway, with the new lookup API, it has become trivial for any project to implement the __ne lookup. It is the first example in the how-to guide: https://docs.djangoproject.com/en/dev/howto/custom-lookups/#a-simple-lookup-example. On Saturday, November 21, 2015 at 11:39:18 AM UTC+1, Carsten Fuchs wrote: > > Am Samstag, 21. November 2015 02:27:42 UTC+1 schrieb Aaron C. de Bruyn: >> >> With all due respect, looking through the ticket and reading responses >> shows me that the 'pro' side has good use cases for __ne, and the 'con' >> side basically says "use exclude" or "a core committer close the ticket, >> stop opening it" with no good reasoning or rationale behind it. >> > > Dito. > > Best regards, > Carsten > > -- 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 firstname.lastname@example.org. 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/8d31a6bf-f435-4579-936b-3206c2c7c2e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.