Kai Mühlbauer

> @mankoff if you have time, can you check your workload against this PR, or review it please? It would be great if Ken could have a look here. At...

> I'm reading this via slow satellite in Antarctica. I'm 'offline'(ish) for another week, then have 2 months of emails and work to catch up on. Reviewing this PR will...

@dcherian I'm good to merge this, we still can iterate later if complaints are coming in.

@dcherian There are still some warnings which could be fixed/silenced with this PR. All try to get behind it now. Update: so some warnings (cast RuntimeWarnings) are not directly connected...

Thanks for raising this. Please see https://github.com/pydata/xarray/issues/6323 for discussion on handling `encoding` in the future. As you already found, `drop_encoding` is the way to go for your use-case. This is...

@tarik Thanks for taking the time to share your thoughts. Regarding the documentation changes we always welcome contributions.

@eivindjahren Thanks for bringing this to attention. From the description it's a bit unclear which engine you want/need to use. You mentioned `engine=netcdf` (should that be `netcdf4`?) and in the...

> Sorry, I ment `engine=scipy`, that was a typo. We have decided to use that in our application for performance reasons. A bit offtopic now, but can you elaborate a...

That seems to be some tricky issue with timezones. The issue already manifests in the DataArray (Variable) creation. The given list of timezone aware datetimes is converted into `pandas._libs.tslibs.timestamps.Timestamp` (wrapped...

> > Is it just me or has this approach not actually preserved the history at all? > > no, that's just the commit for importing the `datatree` repository. Try...