Justus Magin

it looks like `UP007` will have to be converted manually

thanks for finishing this, @dcherian. Let's merge this now, and I'll update the list of required checks after that.

the main use case is indeed to extract additional data, which you'd do immediately after `open_dataset` (after which you could drop the encoding). > Shouldn't `_normalize_path` or `_find_absolute_paths` be able...

my impression of that discussion was that we wanted to either return the encoding in a separate object, or somehow remove the encoding after the first operation (i.e. not carry...

> Would a dataset with this in encoding be round tripped without error? Would be good to test that I'm not opposed to adding an explicit test (since I can't...

as far as I can tell, we could write anything in that encoding (`fsspec` objects, strings, or other things), and it would simply be ignored / dropped before writing.

If I remember correctly, the array API does not support python scalar types (or numpy scalars), so we have to convert them to 0D arrays (see also the discussion in...

what we could do is split the behavior between keyword-argument `data_vars` and positional argument number 1: ```python def __init__(self, vars=None, /, coords=None, attrs=None, *, data_vars=None): ... ``` where `vars` promotes...

true. But I guess people passing `data_vars` explicitly would be less likely to expect creating a coordinate variable from it, so we could shorten the cycle a bit (like, warn...

I don't think we can do a lot here (correct me if I'm wrong, though): the `method` kwarg is handled by the [index implementation](https://github.com/pydata/xarray/blob/1e8f618e9d3754cb892a8438a1a7745aadce2bbf/xarray/core/indexes.py#L561) (in this case, a `pandas.Index`), so...