Davis Bennett
Davis Bennett
One thing about zarr v2 -> v3 that might surprise users is the change from the v2 `compressor` metadata (a single thing) + `filters` (an ordered collection) to the v3...
the metadata classes need tests!
Removes all the v2 code supersedes #1897, #1791 TODO: * [ ] Add unit tests and/or doctests in docstrings * [ ] Add docstrings and API docs for any new/modified...
removes the zarr 2 specific language from the spec, and adds a section recommending against mixing zarr 2 and zarr 3 hierarchies
the v3 spec states that codecs are stored in a JSON array under the key `codecs`. But the spec also states that the list of codecs is [structured](https://github.com/zarr-developers/zarr-specs/blob/daef2bc91a246d24d895276679b6ac9556d7ebb1/docs/v3/core/v3.0.rst?plain=1#L1095-L1100): > ...the...
The `zarr_format` metadata is an [integer](https://github.com/zarr-developers/zarr-specs/blob/main/docs/v3/core/v3.0.rst#zarr_format), but the spec document uses a string identifier that can represent [major and minor versions](https://github.com/zarr-developers/zarr-specs/blob/main/docs/v3/core/v3.0.rst#stability-policy). So, unlike the spec document, the `zarr_format` metadata cannot...
Follow-up from #293 The way the v3 spec describes codecs today is inconsistent with the needs of a large number of users and implementers. Specifically, the spec says that there...
Continuing a conversation from #1661 We have IO operations that can fetch ranges of bytes. That byte range parameter is parameterized by an (optional) 2-tuple of nullable ints, i.e. `tuple[int...
In v2, at array access time it is possible to set whether empty chunks (defined as chunks that are entirely `fill_value`) should be written to storage or skipped. This is...
This PR adds a boolean `array.write_empty_chunks` value to the global config, and uses this value to control whether chunks that are "empty", i.e. filled with values equivalent to the array's...