issues: 438389323
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
438389323 | MDU6SXNzdWU0MzgzODkzMjM= | 2928 | Dask outputs warning: "The da.atop function has moved to da.blockwise" | 691772 | closed | 0 | 4 | 2019-04-29T15:59:31Z | 2019-07-12T15:56:29Z | 2019-07-12T15:56:28Z | CONTRIBUTOR | Problem descriptiondask 1.1.0 moved Related
Code Sample```python import numpy as np import xarray as xr xr.DataArray(np.ones(1000)) d = xr.DataArray(np.ones(1000)) d.to_netcdf('/tmp/ones.nc') d = xr.open_dataarray('/tmp/ones.nc', chunks=10) xr.apply_ufunc(lambda x: 42 * x, d, dask='parallelized', output_dtypes=[np.float64]) ``` This outputs the warning:
Expected OutputNo warning. As user of a recent version of dask and xarray, there shouldn't be any warnings if everything is done right. The warning should be tackled inside xarray somehow. SolutionNot sure, can xarray break compatibility with dask <1.1.0 with some future version? Otherwise I guess there needs to be some legacy code in xarray which calls the right function. Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/2928/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |