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
Increasingly there is a move by Python projects to use pyproject.toml to declare their metadata and dependencies and away from setup.py. Raising this issue to start discussion around how to approach this in Dask-image.
Hm, perhaps one other problem is that with the pyrpoject.toml setup, it looks as though dask-image version 0.0.0 is installed for the development version. That is what appears in the conda list, and I think that'll end up being a bit of a problem. (But if you import dask-image and check the version string, you see the expected version)
Increasingly there is a move by Python projects to use
pyproject.toml
to declare their metadata and dependencies and away fromsetup.py
. Raising this issue to start discussion around how to approach this in Dask-image.Related upstream issues:
setup.py
topyproject.toml
dask#10032setup.py
topyproject.toml
distributed#7622The text was updated successfully, but these errors were encountered: