dask scheduler not recognized as a valid command, despite suggestion from FutureWarning

[DamianBarabonkovQC]

Describe the issue:

When starting a dask scheduler the old way via dask-scheduler, it produces a future warning as such: FutureWarning: dask-scheduler is deprecated and will be removed in a future release; use 'dask scheduler' instead.

However, then when running dask scheduler from the command line produces:

Usage: dask [OPTIONS] COMMAND [ARGS]...
Try 'dask -h' for help.

Error: No such command 'scheduler'.

Something does not work correct in this case.

Environment:

• Dask version: 2022.10.0
• Python version: Python 3.10.6
• Operating System: OSX 12.6
• Install method (conda, pip, source): conda create -n env_name 'dask=2022.10.0'

[jrbourbeau]

Thanks for reporting @DamianBarabonkovQC. FWIW this appears to be a conda-specific issue, so pip installing is a temporary workaround. We're working on a fix for the conda packages. Will keep this issue posted.

[jakirkham]

As James noted, this is a known issue. There have been 2 attempts to fix it, but no success so far. Related threads:

xref: conda-forge/distributed-feedstock#225 (comment)
xref: conda-forge/distributed-feedstock#226
xref: conda-forge/dask-core-feedstock#144

Would suggest just using the old entry points (with -s like dask-scheduler) as they still work. If we don't find a resolution soon, would suggest dropping/softening the deprecation warning (we don't appear to be ready for that).

[jakirkham]

Actually maybe PR ( conda-forge/dask-core-feedstock#146 ) will solve it? Would be good to have others take a look 🙂

[douglasdavis]

I'm relatively confident conda-forge/dask-core-feedstock#146 should end up fixing things