Open soxofaan opened 1 year ago
This is there on backend side, we will of course have to keep XArrayDataCube around for quite a bit. Next step is to update documentation to favour UDF's without XArrayDataCube in the signature.
Indeed, we have to keep XarrayDataCube for legacy reasons and backward compatibility. My questions/proposal is mainly about having a new, simpler UDF signature API
XarrayDataCube
is extremely simple: it just wraps a singlexarray.DataArray
and nothing more. It offers some IO functionality, but that doesn't mean these have to be XarrayDataCube methods. (There is also aplot
method, but I wonder if anybody uses that and I dislike that this drags in a dependency on matplotlib)It's simple, but it creates an extra abstraction layer in working with UDF, possibly making things more confusing than necessary.
can we just drop (the need for)
XarrayDataCube
?