-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataset.__repr__ causing dask to be computed. #820
Comments
Showing a preview of values in a dask dataset can be very convenient for interactive use, so I'm loathe to turn it off entirely. I agree that it's not always useful, though. The current check for remote data is a complete hack that should probably be removed :). What do you think about adding an user configurable option to disable printing lazily computed values in datasets? You could then write something like |
That sounds like a great solution. I'll get a PR up with the |
In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity |
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?
The text was updated successfully, but these errors were encountered: