Justus Magin

how about also accepting a `dict` / kwargs dict (like `assign` / `assign_coords`) to `DataArray.pint.to` and then using different branches for data and coordinates? That way, converting the data and...

Agreed for points 1 (`DataArray` only?) and 3 (`Dataset` only). For 2 there might be a few more options (nothing wrong with this one), but I think we should discuss...

something else that is not a part of the API but in scope for this package (I think?): maybe we could monkeypatch the `repr` of `DataArray`, `Variable` and `Dataset` (or...

from #11: - [x] `pint_xarray.testing`: for testing purposes - [ ] conversion / extraction functions (from `pint_xarray.conversions`)

if we can get the reprs to work (pydata/xarray#2773, hgrecco/pint#1133), improve the documentation and maybe also expose the `pint_xarray.testing` module, we should be close enough to release a initial development...

the HTML `repr` works (`pint` got released today), and there are #20 (docs), #22 (inline repr) and #24 (testing), so once those are merged and the placeholder functions we have...

I was thinking of `plus_minus`, `to_base_units` and `to_system`, which don't have docstrings, work only on the data or raise `NotImplementedError`. Edit: let's continue this in #25

from #61: try to `dequantify` automatically before plotting (see `xarray.plot.plot.label_from_attrs`)

thanks for the report, @raybellwaves, that might actually be a bug in `pint`'s code wrapping `np.where`, or `xarray` does not unpack the `xarray` argument before calling the data's `where`. I'll...

It took me quite a while, but I can now confirm that this is a bug in `pint`: ```python import pint import numpy as np q = pint.Quantity([2, 3, 6,...