Hi James, Am Samstag, 21. November 2015 02:56:45 UTC+1 schrieb James Bennett: > > 8 years later, I still think we should figure out how to make exclude() do > what people expect it to do, rather than implement another lookup type that > overlaps with it. >
What really confuses me is how exclude() is supposed to make __ne redundant? Please see the examples at https://code.djangoproject.com/ticket/5763#comment:14 (sorry I gave a wrong comment number in my initial post, comment 14 is the right one). The comment seems to explain clearly how exclude() can *not* be used where __ne can. 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 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/a7fc93b8-d351-47f0-bf20-1de0365ba917%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
