html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/5980#issuecomment-972095543,https://api.github.com/repos/pydata/xarray/issues/5980,972095543,IC_kwDOAMm_X8458QA3,2584128,2021-11-17T21:46:40Z,2021-11-17T21:46:40Z,NONE,@keewis Thanks for the note.  I originally tried that approach I thought but after this PR I went back and tried again and made more progress so I'm closing this PR.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1051491070
https://github.com/pydata/xarray/pull/5980#issuecomment-968799183,https://api.github.com/repos/pydata/xarray/issues/5980,968799183,IC_kwDOAMm_X845vrPP,14808389,2021-11-15T11:15:51Z,2021-11-15T12:47:42Z,MEMBER,"we usually try to avoid hard-coding support for new array types (`dask` and `sparse` are exceptions), so it's probably better to define `__array_ufunc__` and `__array_function__`. From what I can see the new `__array_namespace__` seems like a much better fit for your library, but that would require some changes to `xarray`, too (we definitely plan on supporting that, but it will take some time).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1051491070