-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move from setup.py
to pyproject.toml
#305
Comments
The only points for discussion I can think of are:
|
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) |
Maybe FlakeHell. This blogpost seems encouraging: https://dev.to/bowmanjd/using-flake8-and-pyproject-toml-with-flakehell-1cn1 |
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: