Michael Niklas

Hmmm, these errors should be fixed in the latest version of this PR. The problem CI is running into is that mypy runs into an unrecoverable error parsing dask, this...

It seems that mypy encountered an unrecoverable runtime error. We should probably report that to mypy, but I cannot reproduce it locally, yet alone create a MVCE.

If that is still an open issue we could merge current main, try to fix the resulting typing problems.

Which mypy version are you using?

Strangely it seems to happen only as part of a Union definition. Also we use tuple and dict all over the place and mypy does not complain anywhere else.

I think we could just add a n additional mypy 3.8 workflow by using the arg `--python-version 3.8`

> pandas raises an error when plotting an empty dataframe: > > ```python > ... > TypeError: no numeric data to plot > ``` Not sure if TypeError is correct?...

Seeing that in another issue (can't find the number) it was discussed to move away from specialized read/write methods and only use `open_dataset`(maybe a `Dataset.read`?) and `ds.write` with engine arguments....

I know that it is more work but I think it would be more beneficial to have this information formated nicely than simply returning some lists. Maybe similar to a...

> One approach might be to add a nice `__str__`, `__repr__`, (or even `_repr_html_`) to the `BackendEntrypoint` class. That way printing a list (or better a dict) of the engine-specific...