Warn (and eventually raise) when client.scatter is used with Active Memory Manager enabled
Open
needs triage
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 778
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 3
Description
Using ``scatter`` is generally not a good idea anymore and doesn't have any effect if the active memory manager is enabled. People are frequently running into this or are using scatter anyway, which is a bad UX and confusing.
We should raise a warning if ``scatter`` is used and point people to delayed and probably raise at some point later or get rid of the method completely.
Contributor guide
Assessment
This issue has not been assessed yet.