oh yes indeed.
Wouldn't it be useful (?) to raise the max_size and check the content_get_range against all situations wrt range limits: the beginning, middle and end of the range (like range(0, 2), range(n, n+2) and range(-3, -1) )?
That's what the three tests are for (test_generate_content_get_range_start, test_generate_content_get_range_end, test_origin_get_range). I did not want to do a single test for all of them, because it means writing the same logic in the test as in the real code, so testing makes less sense
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/486/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/486/console