Kami commented on issue #1431: Add new base storage API methods for partial (range) object downloads URL: https://github.com/apache/libcloud/pull/1431#issuecomment-592747588 This PR is now more or less ready to be merged. I just need to decide (and make any code changes, if necessary) if the ``end_bytes`` offset should be inclusive or not. Currently, it is inclusive. In Python indexing world, end index is not inclusive, but for Range header values, end offset seems to be inclusive for all the providers I tested it with (S3, Google Storage, Azure Blobs). To put it into perspective - if you specify ``Range: bytes=0-5`` header value and the object content is ``0123456789``, you would get ``012345`` value back. This would map to ``content[0: 5 + 1]`` in the Python world. We can hide this behavior from the end user inside the implementation details, we just need to decide which behavior makes the most sense. I'm leaning towards the Python indexing behavior since Libcloud users are working with Python after all.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
