Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make xarray a default dependency #206

Open
JSKenyon opened this issue Apr 21, 2022 · 2 comments
Open

Make xarray a default dependency #206

JSKenyon opened this issue Apr 21, 2022 · 2 comments

Comments

@JSKenyon
Copy link
Collaborator

Description

I believe that the time may have come to make xarray a core dependency rather than an extra. At present, it is optional as dask-ms implements its own stripped down Dataset. Unfortunately, this is introducing more and more maintenance as these stripped down Dataset objects do not implement a host of xarray.Dataset functionality. This means that writing tests can become frustrating as you have to write the tests anticipating two different Dataset implementations (or skip the tests entirely in the absence of xarray, somewhat defeating the point of writing tests). I am personally of the opinion that the xarray.Dataset representation should be fundamental to dask-ms, even if it is less lightweight.

The purpose of this issue is discussion - does anyone object?

@bennahugo
Copy link
Collaborator

bennahugo commented Apr 21, 2022 via email

@JSKenyon
Copy link
Collaborator Author

JSKenyon commented Apr 22, 2022

From offline discussion with Simon I now know that xova relies on the daskms.Dataset. I will continue to think about this as we don't want to break anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants