So, I added a queryset attribute with and empty queryset (suggested in the docs) but DjangoModelPermission continues to ask for get_queryset().

What was the error message ?

The error was the same with and without the queryset attribute suggested.

That my user has not the role that I was checking in get_queryset. So if DjangoModelPermissions only uses the queryset to determine the model name, it is the same to obtain the queryset from the attribute or the method.

Unfortunately this will not be consistent with how DRF works in general.
In any case, get_queryset() should take precedence over queryset because it can adapts the result based on the context.
It looks like the documentation update in #5376 missed the "Using with views that do not include a queryset attribute." section to update and reflect the fact that get_queryset() should be stated instead of queryset.

I understand your point.
But I want to show you my complete example, so maybe I'm using something in a wrong way.

@xordoquy This is other issue (#4129) that I found digging for a similar problem that my fix could help it.

@xordoquy I share a gist with my example of code that fails with the actual version of DjangoModelPermissions.
https://gist.github.com/emilsas/0364e1e756759be6017f19cc8fdb41e8

In your gist, if the user doesn't have a provider_profile then user.provider_profile.products.all() should raise an attribute error or something like that, not return an empty queryset.

@xordoquy I know that raises an exception, but I have a custom permission class that verify that the user has a provider profile (OnlyProvidersPermission). So I think that checking in .get_queryset() and in my custom permission would result in duplicated code.

@xordoquy Hi, could you give me a response please? Thanks

The original issue requires a documentation update to state that get_queryset() should take precedence over queryset.
If you still think there's an issue, we'll need a simple test case that we can reproduce easily first.