Migrate from setuptools to hatchling #874
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
consideRatio
force-pushed
the
pr/drop-setuptools
branch
from
361949e to
5bf1b92
Compare
consideRatio
force-pushed
the
pr/drop-setuptools
branch
6 times, most recently
from
6c3130d to
d6140f7
Compare
consideRatio
force-pushed
the
pr/drop-setuptools
branch
from
d6140f7 to
a31d0db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #740 by transitioning to using hatchling as a build system. This is done especially for dask-gateway-server where setuptools was harder to get configured right when also compiling golang code, but hatchling is also adopted in dask-gateway for project-internal consistency.
Note that
python -m build .would fail if the LICENSE was a symlink with hatchling, so I copied it instead.