Justus Magin

it looks like this has something to do with `zarr=2` vs `zarr=3` (upgrading to `zarr>=3` properly reads back the data), but not sure if that's a bug within `zarr-python=2` or...

> Do you mean that my zarr is version 2 (2.18.3 in the example) and that this is not supported? yes, I think your version is `zarr=2` since you're seeing...

I'd argue that the distro version of python is supposed to only be used for the tools provided by that distro. Either way, `zarr-python=2.18.7` also requires `python>=3.11`, so I don't...

hmm... that one's new, I think we should just delete that branch and let RTD pick the most recent tag. @pydata/xarray, was there a specific purpose behind that branch? If...

I've deleted the `stable` branch and added a ruleset to make sure we don't accidentally break things again. I've also noticed that the version on the entry page for 2025.11.0...

we already have that as the [`pre_install`](https://github.com/pydata/xarray/blob/52283c6b7a3605d14f5e849f36e0b6e90a109ccc/.readthedocs.yaml#L15-L16) hook, so has to be something else that's happening. `git status` says there are no additional changes just before building (see https://app.readthedocs.org/projects/xray/builds/30493408/), so...

It looks like one of the operations (concat, set_index, unstack) calculates the new width wrongly. Could you check if concat on its own or with only 2 stacked variables you...

What if instead we added a method that returned an intermediate object defining only the dataframe protocol? With that, the explicit conversion would be something like `pd.DataFrame(ds.to_df())` or `pl.DataFrame(ds.to_df())` (not...

cc @eni-awowale

that's to be expected, see the [list of operations converting to `numpy`](https://docs.xarray.dev/en/latest/user-guide/duckarrays.html#conversion-to-numpy-as-a-fallback). You can work around this using a custom index, but this is going to be quite a bit...