dask-scheduler command not found with newer versions of distributed

[vladidobro]

Hi!

Describe the issue:

Somewhere between distributed 2025.9.0 and 2026.7.1, the package stopped providing the script dask-scheduler.
I use uv installer in the example, but the same issue is with pip.
The result for me is that dask-kubernetes doesn't start properly

Minimal Complete Verifiable Example:

$ docker run --rm -it ghcr.io/astral-sh/uv:debian sh
# uv venv old-dask
Using CPython 3.13.5 interpreter at: /usr/bin/python3
Creating virtual environment at: old-dask
# . old-dask/bin/activate
(old-dask) # uv pip install dask distributed==2025.9.0
Using Python 3.13.5 environment at: /old-dask
Resolved 19 packages in 457ms
Prepared 19 packages in 250ms
Installed 19 packages in 6ms
 + click==8.4.2
 + cloudpickle==3.1.2
 + dask==2025.9.0
 + distributed==2025.9.0
 + fsspec==2026.6.0
 + jinja2==3.1.6
 + locket==1.0.0
 + markupsafe==3.0.3
 + msgpack==1.2.1
 + packaging==26.2
 + partd==1.4.2
 + psutil==7.2.2
 + pyyaml==6.0.3
 + sortedcontainers==2.4.0
 + tblib==3.2.2
 + toolz==1.1.0
 + tornado==6.5.7
 + urllib3==2.7.0
 + zict==3.0.0
(old-dask) # which dask-scheduler
/old-dask/bin/dask-scheduler
(old-dask) # deactivate
# uv venv new-dask
Using CPython 3.13.5 interpreter at: /usr/bin/python3
Creating virtual environment at: new-dask
# . new-dask/bin/activate
(new-dask) # uv pip install dask distributed==2026.7.1
Using Python 3.13.5 environment at: /new-dask
Resolved 18 packages in 75ms
Prepared 2 packages in 184ms
Installed 18 packages in 8ms
 + click==8.4.2
 + cloudpickle==3.1.2
 + dask==2026.7.1
 + distributed==2026.7.1
 + fsspec==2026.6.0
 + jinja2==3.1.6
 + locket==1.0.0
 + markupsafe==3.0.3
 + msgpack==1.2.1
 + packaging==26.2
 + partd==1.4.2
 + psutil==7.2.2
 + pyyaml==6.0.3
 + sortedcontainers==2.4.0
 + tblib==3.2.2
 + toolz==1.1.0
 + tornado==6.5.7
 + zict==3.0.0
(new-dask) # which dask-scheduler
(new-dask) # dask-scheduler
sh: 11: dask-scheduler: not found

Anything else we need to know?:

Environment:

• Dask version: 2026.7.1
• Python version: 3.12
• Operating System: linux/mac
• Install method (conda, pip, source): uv, pip

[vladidobro]

I see the new docs say the correct command is dask scheduler instead. I am running an outdated version of kubernetes operator, which calls dask-scheduler, maybe it is fixed in the new version of the operator.

So it is maybe expected behaviour, please feel free to close the issue if so.
Thanks!