-
Notifications
You must be signed in to change notification settings - Fork 97
Use hatchling build backend #373
Copy link
Copy link
Closed as not planned
Labels
EnhancementNot a bug, but increases or improves in value, quality, desirability, or attractivenessNot a bug, but increases or improves in value, quality, desirability, or attractivenessInfraAll about infrastructure (GitHub Action, project build etc.)All about infrastructure (GitHub Action, project build etc.)
Description
Metadata
Metadata
Assignees
Labels
EnhancementNot a bug, but increases or improves in value, quality, desirability, or attractivenessNot a bug, but increases or improves in value, quality, desirability, or attractivenessInfraAll about infrastructure (GitHub Action, project build etc.)All about infrastructure (GitHub Action, project build etc.)
Type
Fields
Give feedbackSIze
None yet
Situation
python-semver currently uses the setuptools build backend
Possible Solution/Idea
hatchling seems to be the recommended build backend now. (Tutorial uses it by default.)
Additional context
One of the benefits of switching to hatch (which uses hatchling), besides a nice venv management, would be the possibility of using hatch-semver plugin to semantically version this project.