feat: Migrate from Setuptools to Hatchling as the build backend #528
+5
−9
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.

Description
Migrated from Setuptools to the Hatchling build backend.
Hatchling is very fast, requires zero configuration, and provides good defaults.
Working with Setuptools is a painful process - we need to maintain external files like
MANIFEST.into include/exclude files or folders in the source distribution, whereasin Hatchling this process is straightforward and handled directly within the same
pyproject.toml.Removed files
Test Build
python -m buildORuv build1. Source Distribution
2. Wheel Distribution
Official Hatchling documentation:
https://hatch.pypa.io/