docs: convert notebooks to jupytext scripts - #610
Conversation
zarr 3.3.0 changed codec configuration attributes such as `BloscCodec.cname` and `BytesCodec.endian` from `Enum` members to plain strings, breaking the `.name` accesses in the label writer storage options tests (12 failures). Add a `_codec_value` helper that normalizes both representations, so the tests pass against zarr 3.2 and 3.3 alike. Test-only change; the library code never accessed these attributes. Assisted-by: ClaudeCode:claude-opus-5
for more information, see https://pre-commit.ci
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #610 +/- ##
==========================================
+ Coverage 86.46% 86.89% +0.42%
==========================================
Files 16 16
Lines 2365 2365
==========================================
+ Hits 2045 2055 +10
+ Misses 320 310 -10 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
jo-mueller
changed the title
|
@jni is that roughly how it is done over at napari? In VSCode, it's relatively easy to spawn these scripts from jupyter notebooks. It's probably equally easy to turn them into markdown files with executable python code blocks. |
Yes! Jupytext allows many formats, .py with comments is one, md with python blocks is another. It's a matter of preference which one is preferred, and I guess it depends on the balance of narrative vs code. You're probably missing a whole bunch of dependencies to get napari windows to spawn, I think this is the most important one: |
|
Seems to be working fine! It will be nice in follow-up PRs to add visualisation with napari, but I think it's best to do that later since this build is working. I spot-checked a couple of pages to make sure that the output was the same. |
Agree! Depending on who shows up later today on the napari-ome-zarr-py call, I'll probably merge it later today 👍 |
3 participants
Fixes #604
Rebased on #609