issue_comments: 145118890
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/pull/595#issuecomment-145118890 | https://api.github.com/repos/pydata/xarray/issues/595 | 145118890 | MDEyOklzc3VlQ29tbWVudDE0NTExODg5MA== | 1217238 | 2015-10-02T18:39:30Z | 2015-10-02T18:39:30Z | MEMBER | @jhamman Yep, dask rewrites indexers to getitem. In the case of unsorted indexers, it currently pulls out items by block first: https://github.com/blaze/dask/blob/de3633b2693e67f0acccebda4dfc58332aefb527/dask/array/slicing.py#L461 Wrapping all netCDF4 variables with dask.array might be a viable work around for the netCDF4-python issue, if we make dask a required dependency. We'll probably want to do that after https://github.com/blaze/dask/issues/746 is fixed anyways, though. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
109018309 |