Repository navigation
Switch to hatchling build-backend - #90
Merged
Merged
Conversation
mauvilsa
approved these changes
Jul 7, 2025
mauvilsa
left a comment
Collaborator
There was a problem hiding this comment.
This looks good to me. I have also had problems with poetry and think it would be good to replace it. Thanks for contributing!
Contributor
Author
|
Might want to update the readme at some point. Happy to see this getting some attention |
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
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.
I would recommend not using
poetry, particularly since using any other PEP517 compliant build backend makes things so much easier.I have kept the
devdependency as-is so you can simply runpip install .[dev], but I would recommend against using that because the only dependency there ispre-commit, which is better if you have it installed and managed globally instead of within the venv. Otherwise the other dependencies are split like that becausetestdependencies are often required by packagers, anddocscan be used for the specific documentation build backend.I would also recommend to drop Python<3.8, and even python 3.8 at this point.