issue_comments: 345374271
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/1725#issuecomment-345374271 | https://api.github.com/repos/pydata/xarray/issues/1725 | 345374271 | MDEyOklzc3VlQ29tbWVudDM0NTM3NDI3MQ== | 1197350 | 2017-11-17T21:46:14Z | 2017-11-17T21:46:14Z | MEMBER | I just had to confront and understand how lazy CF decoding worked in order to move forward with #1528. In my initial implementation, I applied chunking to variables directly in My impression after this exercise is that having two different definitions of "lazy" within xarray leads to developer confusion! So I favor putting dask more central in xarray's data model. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
274797981 |