Strange, I must have replied to the author only. It seems as though I was a goof and after looking through the source I discovered how the model manager handles functions for the queryset.
xyz.objects.get_query_set()._filter_or_exclude(...) does the trick. I assumed it wasn't available without understanding how it is made available in the first place. - Shane On Apr 11, 11:04 am, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Mon, Apr 11, 2011 at 11:23 AM, sh...@bogomip.com <spence...@gmail.com> > wrote: > > 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. > > Just go ahead and use it if you find it useful! The Python philosophy > is that we're all "consenting adults", so there's nothing preventing > you from using a so-called-private function if you find it useful. As > long as you're aware that you're using an API prone to change between > versions you'll be just fine. Test those parts of your code carefully > when you upgrade Django and you won't get bitten if it changes. > > Jacob -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
