issues: 804694945
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 804694945 | MDExOlB1bGxSZXF1ZXN0NTcwNDE5NjIz | 4884 | Compatibility with dask 2021.02.0 | 6213168 | closed | 0 | 0 | 2021-02-09T16:12:02Z | 2021-02-11T18:33:03Z | 2021-02-11T18:32:59Z | MEMBER | 0 | pydata/xarray/pulls/4884 | Closes #4860 Reverts #4873 Restore compatibility with dask 2021.02.0 by avoiding improper assumptions on the implementation details of This PR does not align xarray to the new dask collection spec (https://github.com/dask/dask/issues/7093), as I just realized that Datasets violate the rule of having all dask keys with the same name if they contain more than one dask variable - and cannot do otherwise. So I have to change the dask collection spec again to accommodate them. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4884/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |