Skip to content
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

Remove Dask as a hard dependency of Datashader #1349

Open
Azaya89 opened this issue Jul 3, 2024 · 1 comment · May be fixed by #1350
Open

Remove Dask as a hard dependency of Datashader #1349

Azaya89 opened this issue Jul 3, 2024 · 1 comment · May be fixed by #1350

Comments

@Azaya89
Copy link

Azaya89 commented Jul 3, 2024

Is your feature request related to a problem? Please describe.

When using Datashader (either directly or interactively as a parameter in hvPlot) on a project that doesn't use Dask, you get a future warning of the form:

FutureWarning: Dask dataframe query planning is disabled because dask-expr is not installed.

You can install it with `pip install dask[dataframe]` or `conda install dask`.
This will raise in a future version.

  warnings.warn(msg, FutureWarning)

However, this warning is removed when Dask is added as a dependency of the project

Describe the solution you'd like

It will be nice to NOT have dask as a dependency for using datashader, especially when the specific case doesn't require the use of Dask.

Describe alternatives you've considered

I have temporarily added Dask as a dependency for the current examples I've encountered it

Additional context

Example screenshot - Using rasterize in hvPlot:
image

@hoxbro hoxbro linked a pull request Jul 3, 2024 that will close this issue
@jbednar
Copy link
Member

jbednar commented Jul 3, 2024

Thanks! Right now dask-core is a hard dependency, and dask-expr (brought in by installing dask) turns out to be a soft dependency. Ideally, as in #1350, we won't have any dependency at all, so that users not installing dask will never see anything to do with Dask to confuse them. Hope #1350 works well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants