Skip to content

fix: use public attribute in zarr parser#916

Merged
TomNicholas merged 1 commit intozarr-developers:mainfrom
maxrjones:use-public-api
Mar 10, 2026
Merged

fix: use public attribute in zarr parser#916
TomNicholas merged 1 commit intozarr-developers:mainfrom
maxrjones:use-public-api

Conversation

@maxrjones
Copy link
Copy Markdown
Member

Fixes the bug revealed in #831 (comment) for older Zarr-Python versions. follow-up to #892, so doesn't need a release note.

Also adds the zarr dependency group to more tests environments.

@maxrjones maxrjones requested review from TomNicholas and norlandrhagen and removed request for TomNicholas March 10, 2026 19:38
@TomNicholas TomNicholas merged commit 35bf596 into zarr-developers:main Mar 10, 2026
13 checks passed
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.18%. Comparing base (333070f) to head (e74c2af).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #916   +/-   ##
=======================================
  Coverage   89.18%   89.18%           
=======================================
  Files          33       33           
  Lines        2052     2052           
=======================================
  Hits         1830     1830           
  Misses        222      222           
Files with missing lines Coverage Δ
virtualizarr/parsers/zarr.py 94.41% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@maxrjones maxrjones self-assigned this Mar 16, 2026
TomNicholas added a commit to TomNicholas/VirtualiZarr that referenced this pull request Mar 23, 2026
- zarr-developers#880 Fix dmrpp error handling
- zarr-developers#868 Fix error with Zarr-Python 3.1.0
- zarr-developers#924 Fix coordinate name issue
- zarr-developers#916 Fix ZarrParser to use public attribute

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TomNicholas added a commit that referenced this pull request Mar 23, 2026
* add empty release notes

* Fix wrong PR link references in release notes

- Line 57: PR text said #927 but URL pointed to #932 (correct PR)
- Line 115: PR text said #565 but URL pointed to #822 (correct PR)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Move PR #818 from v2.2.0 to unreleased section

This PR was merged after v2.4.0 but was incorrectly listed
under the v2.2.0 release notes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add missing bug fixes to unreleased section

- #880 Fix dmrpp error handling
- #868 Fix error with Zarr-Python 3.1.0
- #924 Fix coordinate name issue
- #916 Fix ZarrParser to use public attribute

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add missing documentation entries to unreleased section

- #918 FAQ answer on "why still write native zarr?"
- #893 Update FAQ regarding virtualizing existing Zarr V2 data
- #937 R2 docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add missing internal change #909 to unreleased section

Compiled regular expressions for improved performance.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add missing documentation entries to v2.4.0 release notes

- #855 Add example of virtualizing GOES
- #856 Update kerchunk comparison in FAQ

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Add missing entries to v2.2.0 release notes

- #829 Raise informative error on Zarr V2 parsing with Zarr-Python<3.1.3
- #805 Revert unnecessary dtype conversion in icechunk writer

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

2 participants