Justus Magin

you have two choices: - use `pint-xarray`'s versions of `loc` / `sel`: `yq.pint.loc[{"x": Q_(1, "s")}]` or `yq.pint.sel(x=Q_(1, "s"))` - install `pint-xarray` from `main` and try out the new `PintIndex`. This...

closing as 0.5.0 brought the `PintIndex`, so now the advice is just to upgrade

this idea has come up before, see pydata/xarray#7348. You could imagine loading the entrypoint library whenever this particular attribute is accessed, but `__getattr__` on `Dataset` and `DataArray` is already complicated...

that could work, with the downside that now the import time has increased simply by the presence of the library. Given that people have repeatedly complained about long import times...

Thanks for the report, @martijnvandermarel. This looks like a copy/paste error and is definitely not intentional (and `Dataset` seems to also be affected). I'd be happy to take a PR...

should have been closed by #270

> Does anyone immediately see why the zarr engine might not be registered? I don't, but usually this means that the backend library (in this case, `zarr` or its dependencies)...

I can reproduce locally, and `python -c 'import zarr'` fails because `donfig` and `crc32c` have not been pulled in as dependencies (does this need to be changed upstream in `zarr`?)....

Over the past two years we've been trying to release at least once a month. This didn't always work out exactly (there's no release in August this year, for example),...

@dcherian, there's a new groupby failure: ``` xarray/tests/test_groupby.py::test_gappy_resample_reductions[any]: IndexError: bool index 1 has shape (11,) instead of (13,) ``` Do you have any idea about what could cause this?