Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 2 commits
- 14 files changed
- 2 contributors
Commits on Feb 11, 2025
-
(feat): full v2 compat via python fallback (#84)
* chore(deps): bump zarr to 3.0.0rc1 * fmt * (feat): python fallack * (fix): dtypes * (fix): `object` dtypes + `v2` tests * (fix): `object` dtypes + `v2` tests * (fix): `object` dtypes + `v2` tests * (fix): `object` dtypes in rust * (fix): blosc support * (refactor): handle `None` fill-value more gracefully * fix: V2 codec pipeline creation * fix: zfpy/pcodec metadata handling * (fix): fall back for unsupported codecs * (fix): our decode codec pipeline does not support vlen * (fix): string dtype test to match zarr-python * (chore): add note * (fix): ruff * (fix): rustfmt * (fix): `pyi` * (fix): try removing zarr main branch dep * fix: use upstream implicit fill values * fix: use upstream metadata handling There is a lot of additional logic already taken care of by `zarrs`, like handling multiple versions of codec metadata. * fix: cleanup fill value handling for string dtype * Revert "fix: cleanup fill value handling for string dtype" This reverts commit 6ff6c2b. * fix: cleanup fill value handling for string dtype * fix: fmt and clippy warnings * fix: zarr-python 0 fill value handling --------- Co-authored-by: Lachlan Deakin <[email protected]>
Commits on Feb 14, 2025
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.1.1...v0.1.2