Migrate from setup.py to pyproject.toml #1238
Merged
Conversation
This file contains 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
jsfehler
force-pushed
the
use_pyproject
branch
from
cebd10b to
33d9b78
Compare
fsouza
approved these changes
Feb 14, 2024
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've chosen hatchling over setuptools as I believe it offers a good value proposition for Python projects that don't require external modules or compilation of dependencies. For more information: https://hatch.pypa.io/dev/why/
This doesn't prevent us from using the
buildpackage as a front-end. UsingHatchas a replacement fortoxandbuildcould be done in the future, but isn't necessary immediately.