Drop runtime dependency to setuptools

[crusaderky]

setuptools now remains exclusively in setup.py and conda meta.yaml.
It is also optionally used by versioneer, with a transparent fallback to distutils if it's not already loaded.

twin of

• Drop runtime dependency to setuptools dask#8855

xrefs

• Drop setuptools from distributed recipe #5963
• drop pkg_resources in favour of importlib.metadata #5923
• Set ceiling for setuptools dask#8509

[crusaderky]

I can see a wealth of differences between

• dask/continuous_integration/recipe/meta.yaml
  and
• distributed/continuous_integration/recipes/dask/meta.yaml

I expect one of the two files to be unused?

CC @jsignell

[github-actions]

Unit Test Results

       12 files  +       4         12 suites  +4   6h 38m 10s ⏱️ + 2h 37m 5s
  2 675 tests +       3    2 591 ✔️ +     12    81 💤  -   11  3 ❌ +2 
15 954 runs  +5 298  15 089 ✔️ +5 012  862 💤 +284  3 ❌ +2 

For more details on these failures, see this check.

Results for commit a7896e9. ± Comparison against base commit ed48736.

♻️ This comment has been updated with latest results.

[crusaderky]

All failures unrelated.
linting failure: #6019

[jsignell]

My understanding is that there recipes are exclusively used for nightly builds. @charlesbluca @jakirkham

[charlesbluca]

My understanding is that there recipes are exclusively used for nightly builds

Correct, both are used in this workflow to build / publish nightlies on every commit.

I expect one of the two files to be unused?

Both are being used, with dask/continuous_integration/recipe/meta.yaml generating dask-core nightlies and distributed/continuous_integration/recipes/dask/meta.yaml generating dask metapackage nightlies