dask / dask/distributed

client.compute() does not dive into collections

Open
#1,070 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

dask.compute dives into collections:

```
d = dask.delayed(1)
dask.compute({'a': d, 'b': d})

>> ({'a': 1, 'b': 1},)
```

But client.compute does not:

```
c = distributed.Client()
c.compute({'a': d, 'b': d}, sync = True)

>> {'a': Delayed('int-dbc2b219-003d-40ec-b60c-0e171196de2e'),
'b': Delayed('int-dbc2b219-003d-40ec-b60c-0e171196de2e')}
```

Is this the intended behaviour or should it be uniform across the compute methods?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.