Skip to content

two offsets or offset + size? #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rabernat opened this issue Nov 18, 2020 · 2 comments
Closed

two offsets or offset + size? #4

rabernat opened this issue Nov 18, 2020 · 2 comments

Comments

@rabernat
Copy link
Contributor

In most of original zarr issue discussion (zarr-developers/zarr-python#556), offsets were specified with offset, size. In this spec, you are doing start, stop. It seems like offset, size will probably be slightly smaller as a text representation. I'm curious how you made that choice?

@martindurant
Copy link
Member

I believe it was the API of the "fetch" functions littered throughout fsspec. So... mental convenience.

@manics
Copy link

manics commented Nov 19, 2020

I think offset, size is also less likely to cause confusion across different languages and systems. For example Python uses inclusive-exclusive ranges while HTTP partial requests are inclusive-inclusive.

moradology pushed a commit to moradology/kerchunk that referenced this issue Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants