      """
      View for testing custom max_paginate_by usage
      """
      model = BasicModel
      paginate_by = 5
      max_paginate_by = 3
      paginate_by_param = 'page_size'
  
  
  class IntegrationTestPagination(TestCase):
      """
 
</s> remove         self.assertEqual(response.data['results'], self.data[:3])
 </s> add         self.assertEqual(response.data['results'], self.data[:5]) </s> remove         If max_paginate_by is set and it less than paginate_by, new kwarg should limit requests for review.
 </s> add         If max_paginate_by is set, it should limit page size for the view. </s> remove         If max_paginate_by is set, new kwarg should limit requests for review.
 </s> add         If max_paginate_by is set, but client does not specifiy page_size,
        standard `paginate_by` behavior should be used. </s> remove def strict_positive_int(integer_string):
 </s> add def strict_positive_int(integer_string, cutoff=None):
    paginate_by = 3
    max_paginate_by = 5
      """
      View for testing custom max_paginate_by usage
      """
      model = BasicModel
    paginate_by = 3
    max_paginate_by = 5
    paginate_by = 3
    max_paginate_by = 5
      paginate_by_param = 'page_size'
  
  
  class IntegrationTestPagination(TestCase):
      """
keep keep keep keep replace replace keep keep keep keep keep
 Tweak MAX_PAGINATE_BY behavior in edge case.

Always respect `paginate_by` settings if client does not specify page
size.  (Even if the developer has misconfigured, so that `paginate_by >
max`.) 
rest_framework/tests/test_pagination.py