feat: Use hatchling as the build backend #3
Merged
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.
To be able to achieve ssl-hep/ServiceX_frontend#352 all dependencies need to be on conda-forge as well. conda-forge requires that all distributions also package their LICENSE file, and conda-forge builds the distributions from either Git source code or (preferably) a sdist on PyPI.
make-it-sync
's sdist doesn't include the LICENSE fileAs this requires making a new release that includes LICENSE information, I updated the build backend from
setuptools
+distutils
tohatchling
.@gordonwatts If this all looks acceptable, after this is merged could you make a
v0.2.0
(minor as this drops Python 3.6 as it is very EOL) release on PyPI?