Closed tomwhite closed 1 month ago
this functionality is handled by Group.create_array
(that's the async function, which is wrapped by a method with the same name on the synchronous group class)
It's an incompatible change - and it doesn't allow the data to be passed in to the function.
noted. my personal view is that create_array
is a better name for this routine than array
and so long-term that function should be what people use, and I do think create_array
should be changed to take a data
parameter. As a stop-gap measure for v2 compatibility, perhaps we could implement SyncGroup.array
as a wrapper around SyncGroup.create_array
, with a loud deprecation warning? Not sure what the deprecation window should be.
thoughts @jhamman ?
I strongly favor not breaking existing public Zarr API with the V3 release as much as feasible. Doing so will make users unhappy. Yes the API may be too broad. So let's deprecate things carefully, rather than releasing breaking changes.
Zarr version
3.0.0a1
Numcodecs version
0.12.1
Python Version
3.11.9
Operating System
Mac
Installation
pip
Description
There is no
Group.array
method in v3, which is a fairly common way of creating nested arrays.Steps to reproduce
Additional output
No response