build: move from setup.py to pyproject.tom and use hatch#2
Merged
Conversation
tlambert03
changed the title
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
1 participant
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.
we should discuss this one, but opening a PR for something concrete to look at:
this replaces setup.py with an all-pyproject build using hatch...
I'll note that using hatch is in addition to replacing setup.py with pyproject.toml (setuptools also has beta support for an all-pyproject.toml build). I happen to like hatch quite a bit and there's a fair amount of momentum behind it in the community. I can also make an intermediate PR that keeps setuptools.
lastly, there's a discussion to be had about versioning as well (changes are made here, and could be undone, we just need to discuss your personal preferences for how you like to version stuff)