issue_comments: 264510264
This data as json
| 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/issues/979#issuecomment-264510264 | https://api.github.com/repos/pydata/xarray/issues/979 | 264510264 | MDEyOklzc3VlQ29tbWVudDI2NDUxMDI2NA== | 5356122 | 2016-12-02T17:23:46Z | 2016-12-02T17:23:46Z | MEMBER | As an end user, it would be really nice to not have to worry about chunks at all. I'd like to write the same code in xarray using Numpy and have it do the right thing in dask transparently. It seems like dask is moving in this direction (see Automatic blocksize for read_csv dask/dask#1147). Agree with @shoyer that these features belong in dask. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
172291585 |