-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
No, I can't think of any good reason not to simplify this to just use
xarray -- it is a stable package.
…On Thu, Apr 21, 2022 at 9:23 AM JSKenyon ***@***.***> wrote:
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?
—
Reply to this email directly, view it on GitHub
<#206>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4RE6SVRBAXAWFPOEOBVCDVGD66VANCNFSM5T6JGJFA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
--
Benjamin Hugo
PhD. student,
Centre for Radio Astronomy Techniques and Technologies
Department of Physics and Electronics
Rhodes University
Junior software developer
Radio Astronomy Research Group
South African Radio Astronomy Observatory
Black River Business Park
Observatory
Cape Town
|
From offline discussion with Simon I now know that xova relies on the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I believe that the time may have come to make
xarray
a core dependency rather than an extra. At present, it is optional asdask-ms
implements its own stripped downDataset
. Unfortunately, this is introducing more and more maintenance as these stripped downDataset
objects do not implement a host ofxarray.Dataset
functionality. This means that writing tests can become frustrating as you have to write the tests anticipating two differentDataset
implementations (or skip the tests entirely in the absence ofxarray
, somewhat defeating the point of writing tests). I am personally of the opinion that thexarray.Dataset
representation should be fundamental todask-ms
, even if it is less lightweight.The purpose of this issue is discussion - does anyone object?
The text was updated successfully, but these errors were encountered: