I pinned setuptools in the build environment for the dask-gateway-server package to ==63.* as I didn't know another way of resolving the issue.
setuptools in the build environment for dask-gateway-server is now pinned to 63 because 64+ has introduced the "editable_wheel" command to replace the "develop" command, and the editable_wheel command doesn't respect package_data config. We rely on that to get our golang built proxy accessible currently!
Message when using "setuptools>=64" during "pip install --editable .":
Editable install will be performed using a meta path finder.
Options like package-data, include/exclude-package-data or
packages.find.exclude/include may have no effect.
The problematic result is that we end up without a golang binary in dask_gateway_server/proxy/dask-gateway-proxy.
I pinned setuptools in the build environment for the dask-gateway-server package to
==63.*
as I didn't know another way of resolving the issue.setuptools in the build environment for dask-gateway-server is now pinned to 63 because 64+ has introduced the "editable_wheel" command to replace the "develop" command, and the editable_wheel command doesn't respect package_data config. We rely on that to get our golang built proxy accessible currently!
Message when using "setuptools>=64" during "pip install --editable .":
The problematic result is that we end up without a golang binary in dask_gateway_server/proxy/dask-gateway-proxy.
Related