Am 11.07.19 um 19:20 schrieb Robert Schindler:
Sure it is, but I, personally, find it more appealing to have the functionality as part of the Q object itself, because it operates on a single Q object as input and returns another one, which makes this an ideal candidate for an object member, imho. Not to say that it must be in Django directly.
Oops, should have been: "I don't want to say it must be in Django directly."
Best regards Robert -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0a554a71-a9cd-c411-f417-213f2e7025c4%40efficiosoft.com. For more options, visit https://groups.google.com/d/optout.
