Please find it in your hearts to expose filter_or_exclude at a global level.

I often have to filter or exclude based on a search boolean. Writing
duplicate code for both queries or selecting which of the two
functions using my own function feels horribly repetitive since a
function doing exactly that exists in the base model query manager.

IMHO (which is very H) _filter_or_exclude should be public. I can't
find a compelling reason for it not to be other than it has never
been.

- Shane

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.