issues: 956103236
This data as json
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
956103236 | MDU6SXNzdWU5NTYxMDMyMzY= | 5648 | Duck array compatibility meeting | 35968931 | open | 0 | 31 | 2021-07-29T18:31:52Z | 2021-10-12T18:26:17Z | MEMBER | Proposal: hold a high-level inter-library meeting to sort out roadblocks in the duck-array wrapping efforts.Whilst trying to get dask, pint and xarray all working nicely together, I couldn't help but notice there are important issues which conclude with a shared sentiment that "we just need to make a decision as to what wraps what" but since then have had essentially no codified consensus, and hence no progress for the past year. Multiply-nested duck-array wrapping is complicated and involves a lot of separate libraries (as this graph of potential wrappings shows), but could be an amazingly powerful feature! I suggest that as asynchronous discussion hasn't moved this forward, we should instead hold a (hopefully one-off) meeting to make these high-level design decisions. I'm happy to arrange the meeting, but for this to work we ideally need attendees who understand the issues from the perspective of each of the main libraries involved - some suggestions: - xarray (@shoyer and @keewis) - dask (@mrocklin?) - pint (@jthielen) - cupy? (@jacobtomlinson?) - sparse? (@crusaderky?) - pytorch?? (@rgommers??) Possible Agenda (please suggest additions!):
Background reading
Some related issues (there are many more - please add)
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5648/reactions", "total_count": 9, "+1": 4, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 5, "rocket": 0, "eyes": 0 } |
13221727 | issue |