You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the nebari-dask meta-package came about because at one point it was thought that it was necessary to pin a specific version of dask to a specific version of dask-gateway, but this is not the case anymore.
So if it's not necessary to pin a version of dask to a version of dask-gateway:
dask should not be pinned in the nebari-dask meta-package.
if dask is not pinned in the nebari-dask meta-package, then it's just dask-gateway being pinned in the meta-package.
if it's just dask-gateway being pinned in the nebari-dask meta-package we should get * rid of the nebari-dask metapackage and just pin dask-gateway in the various environments!
The text was updated successfully, but these errors were encountered:
Describe the bug
I think the
nebari-dask
meta-package came about because at one point it was thought that it was necessary to pin a specific version ofdask
to a specific version ofdask-gateway
, but this is not the case anymore.So if it's not necessary to pin a version of
dask
to a version ofdask-gateway
:dask
should not be pinned in thenebari-dask
meta-package.dask
is not pinned in thenebari-dask
meta-package, then it's justdask-gateway
being pinned in the meta-package.dask-gateway
being pinned in thenebari-dask
meta-package we should get * rid of thenebari-dask
metapackage and just pindask-gateway
in the various environments!The text was updated successfully, but these errors were encountered: