Migrate build system from setuptools to hatchling#136
Merged
Conversation
Replace setuptools + setuptools-scm with hatchling + hatch-vcs for a lighter, more modern build backend. All metadata, versioning, and package data (py.typed) are preserved. https://claude.ai/code/session_01Wwr1CDbtn58p2EAohRFB5z
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR migrates the project's build system from setuptools to hatchling, modernizing the build configuration and dependency management.
Key Changes
setuptools.build_metatohatchling.buildsetuptools>=64andsetuptools-scm>=8withhatchlingandhatch-vcs[tool.setuptools-scm]to[tool.hatch.version]configuration with VCS-based versioning[tool.setuptools.package-data]to[tool.hatch.build.targets.wheel]0.0.0for builds without VCS metadataImplementation Details
The migration preserves all existing functionality while adopting hatchling's configuration format. The
py.typedmarker file is now included through hatchling's wheel target configuration, and version management continues to use VCS information with the same fallback behavior.https://claude.ai/code/session_01Wwr1CDbtn58p2EAohRFB5z