id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
653430454,MDU6SXNzdWU2NTM0MzA0NTQ=,4208,Support for duck Dask Arrays,3460034,closed,0,,,18,2020-07-08T16:23:12Z,2020-09-02T18:28:12Z,2020-09-02T18:28:12Z,CONTRIBUTOR,,,,"https://github.com/pydata/xarray/issues/525#issuecomment-531603357 raised the idea of adding ""duck Dask Array"" support to xarray as a way to handle xarray > Pint Quantity > Dask Array wrapping in a way that still allowed for most of xarray's Dask integration to work properly. With @rpmanser working on implementing the Dask collection interface in Pint (https://github.com/hgrecco/pint/pull/1129), I thought it best to elevate this to its own issue to track progress and discuss implementation on xarray's side (since hopefully @rpmanser or I can get started on it soon).

Two initial (and intertwined) discussion points that I'd like to bring up (xref https://github.com/hgrecco/pint/pull/1129#issuecomment-655197079):

- How should xarray check for a duck Dask Array?
- Is it acceptable for a Pint Quantity to always have the Dask collection interface defined (i.e., be a duck Dask array), even when its magnitude (what it wraps) is not a Dask Array?

cc @keewis, @shoyer, @crusaderky ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/4208/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue