DOC: confusing statement about write_empty_chunks default

[tlambert03]

Describe the issue linked to the documentation

in the performance docs https://zarr.readthedocs.io/en/latest/user-guide/performance/#empty-chunks it says:

If you know that your data will form chunks that are almost always non-empty, then there is no advantage to the optimization described above. In this case, creating an array with write_empty_chunks=True (the default) will instruct Zarr to write every chunk without checking for emptiness.

in the docs source it's here

but this contradicts what I see when I check the zarr config (in a clean env, with only zarr installed and imported)

➜ uv run --with zarr python -c "import zarr; print(zarr.config.get('array.write_empty_chunks'))"
Installed 8 packages in 49ms
False

am I misunderstanding something? or are the docs wrong about the default value for write_empty_chunks

Suggested fix for documentation

No response

[d-v-b]

i think the docs are simply wrong here, and probably need to be updated to be kept in sync with the actual config. I'd love an automatic way to catch drift like this. maybe the best thing would be an inlne python code snippet in the docs that assumes the default claimed by the defaults, and which would fail when we run our doctests

[tlambert03]

ok, thanks for confirming!

[RituDSML]

The docs are now built with MkDocs (see .readthedocs.yaml), so the suggestion about using Sphinx doctests to catch drift may not apply in the current setup.