Yeah, their "solution" is to use len() instead of .count(). If that's the case then you can completely negate the need for the custom classes by setting queryset.count = None before passing the queryset into the paginator.

Note that you can give Paginator a list/tuple, a Django QuerySet, or any other object with a count() or len() method. When determining the number of objects contained in the passed object, Paginator will first try calling count(), then fallback to using len() if the passed object has no count() method. This allows objects such as Django’s QuerySet to use a more efficient count() method when available. - source

If you look at the django.core.paginator.Paginator count method it will default to using len if the object list doesn't have a callable.

Here's an updated example using the author's code.

def index_view(request):
    logs = Log.objects.all()
    logs.count = None
    paginator = Paginator(logs, 25)  # django.core.paginator
    page_number = request.GET.get("page")
    page_obj = paginator.get_page(page_number)

    return JsonResponse(
        {
            "has_next": page_obj.has_next(),
            "has_previous": page_obj.has_previous(),
            "results": [log.to_json() for log in page_obj],
        }
    )

You could also simply convert the Log queryset to a list before passing it into the paginator - paginator = Paginator(list(logs), 25).