issues: 146812468
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
146812468 | MDU6SXNzdWUxNDY4MTI0Njg= | 820 | Dataset.__repr__ causing dask to be computed. | 15901813 | closed | 0 | 3 | 2016-04-08T04:43:18Z | 2019-10-01T04:18:38Z | 2019-10-01T04:18:37Z | NONE | Printing a Dataset object will show array values (#206), but it will also cause a dask-backed array to be computed so that the data variable values can be computed:
When a DataArray is printed, it doesn't compute values when using dask:
There is a check to make sure the data is not remote, but not based on dask status, see: https://github.com/pydata/xarray/blob/master/xarray/core/formatting.py#L173 Is there a way to indicate that computing a particular dask is an expensive operation and it should not be calculated? |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/820/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |