Justus Magin

a tip: ```python ds['temp'] = ds['temp'].pint.to('degree_Celsius') ``` can also be written as ```python ds = ds.pint.to({"temp": "degree_Celsius"}) ``` and while right now most operations are supported, some of the most...

FYI this: > Instructing users to either import cf-xarray before pint-xarray or set will not be necessary anymore with hgrecco/pint#1366

I can't point you to a specific place, but it seems there's work in progress to use `awkward` to represent polylines / polygons in memory which would make this suggestion...

see pydata/xarray#4285 for some related discussion

this feels pretty similar to `.pint.dequantify().drop_attrs("units")` (if we had something like `.drop_attrs`), but it's true that `.data.magnitude` is much more accessible than that. So I guess defining `.pint.magnitude` to return...

I do agree to make the change, but I would argue that `.pint.dequantify()` should be used to convert between `DataArray(pint(dask(numpy)))` and `DataArray(dask(numpy))` (and if that doesn't work we should fix...

I'm not particularly attached to having it raise `ValueError`, but there were a few issues I ran into that could be avoided that way. What I remember is that choosing...

I just saw [PEP-654](https://www.python.org/dev/peps/pep-0654/), which seems like it would resolve this (and much better than a single exception class could, if I understand correctly): we'd define a `PintExceptionGroup` (or a...

There's also PEP 678 which allows attaching additional information to a exception. In our case, that would be the variable name and, in the case of `quantify`, the source of...

we could also provide work-arounds for operations like `rolling` or `ffill` that, due the functions and libraries they use (i.e. `bottleneck`, `numbagg`, `scipy`, `numpy.lib`, etc., but also `numpy.vectorize`), won't be...