Yes, it's a little weird, but the way filtersets work with django-filter, they have a qs property, which you can also ignore because they define the `__iter__`, `__len__` and `__getitem__` magic method that hide this for you (see https://github.com/alex/django-filter/blob/develop/django_filters/filterset.py#L247 )

In this case, I need the real qs, because the only way to pass information to DRF is by attaching custom attributes on the returned queryset (not the issue here because it's tastypie, we are directly instantiating the filterset ourselves instead of relying on DRF to do it for us)