issues: 166287789
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 166287789 | MDU6SXNzdWUxNjYyODc3ODk= | 902 | Pickle and .value vs. dask backend | 6213168 | closed | 0 | 6 | 2016-07-19T09:34:30Z | 2016-11-14T16:56:44Z | 2016-11-14T16:56:44Z | MEMBER | Pickling a xarray.DataArray with dask backend will cause it to resolve the .data to a numpy array. This is not desirable, as there's legitimate use cases where you may want to e.g. save a computation for later, or send it somewhere across the network. Analogously, auto-converting a dask xarray to a numpy xarray as soon as you invoke the .value property is probably nice when you are working on a jupyter terminal, but not in a general purpose situation, particularly when xarray is used at the foundation of a very complex framework. Most of my headaches so far have been caused trying to figure out when, where and why the dask backend was replaced with numpy. IMHO a module-wide switch to disable implicit dask->numpy conversion would be a nice solution. A new method, compute(), could explicitly convert in place from dask to numpy. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/902/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |