Skip to content

DOC: fix v3 migration guide store table #3850

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.

Sign up for GitHub

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

Open
nuglifeleoji wants to merge 2 commits into
base: main
Choose a base branch
from
+7 −5
Open

DOC: fix v3 migration guide store table #3850

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e7a4e1
DOC: remove result="ansi" causing empty code blocks in user guide
Mar 30, 2026
4fe1859
DOC: fix store migration guide: remove broken row, add LRUStoreCache …
Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/user-guide/experimental.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ such as a remote store for source data and a local store for persistent caching.

The CacheStore provides significant performance improvements for repeated data access:

```python exec="true" session="experimental" source="above" result="ansi"
```python exec="true" session="experimental" source="above"
import time

# Benchmark reading with cache
Expand Down Expand Up @@ -121,7 +121,7 @@ cache = CacheStore(

**cache_set_data**: Controls whether written data is cached

```python exec="true" session="experimental" source="above" result="ansi"
```python exec="true" session="experimental" source="above"
# Cache data when writing (default)
cache = CacheStore(
store=source_store,
Expand All @@ -141,7 +141,7 @@ cache = CacheStore(

The CacheStore provides statistics to monitor cache performance and state:

```python exec="true" session="experimental" source="above" result="ansi"
```python exec="true" session="experimental" source="above"
# Access some data to generate cache activity
data = zarr_array[0:50, 0:50] # First access - cache miss
data = zarr_array[0:50, 0:50] # Second access - cache hit
Expand Down Expand Up @@ -232,7 +232,7 @@ of source and cache stores for your specific use case.

Here's a complete example demonstrating cache effectiveness:

```python exec="true" session="experimental-final" source="above" result="ansi"
```python exec="true" session="experimental-final" source="above"
import numpy as np
import time
from tempfile import mkdtemp
Expand Down
4 changes: 3 additions & 1 deletion docs/user-guide/v3_migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,6 @@ The following stores have been renamed or changed:
| `DirectoryStore` | [`zarr.storage.LocalStore`][] |
| `FSStore` | [`zarr.storage.FsspecStore`][] |
| `TempStore` | Use [`tempfile.TemporaryDirectory`][] with [`LocalStore`][zarr.storage.LocalStore] |
| `zarr.


A number of deprecated stores were also removed.
Expand All @@ -152,6 +151,9 @@ See issue #1274 for more details on the removal of these stores.
N5 formatted data.
- `ABSStore` - use the [`zarr.storage.FsspecStore`][] instead along with fsspec's
[adlfs backend](https://github.com/fsspec/adlfs).
- `LRUStoreCache` - no direct equivalent in Zarr-Python 3. Caching behaviour can be
achieved by wrapping a store with a third-party caching layer, or by using an
`FsspecStore` with a caching filesystem (e.g. `fsspec.implementations.caching`).
- `DBMStore`
- `LMDBStore`
- `SQLiteStore`
Expand Down
Loading