-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
#7622
Comments
Thanks @jakirkham! I'll suggest we consolidate conversation over in dask/dask#10032 for the time being. My guess is we'll end up doing the same thing, at the same time, in |
related to dask#7622
related to dask#7622
@jakirkham which build tool do we want to use eventually? I have a PR open #7629 which uses setuptools and versioneer via PEP 517, but what is the end goal? Should we be aiming at |
Continuing to use |
related to dask#7622
related to dask#7622
related to dask#7622
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.dask/dask#10032
The text was updated successfully, but these errors were encountered: