Switch build-backend from setuptools to hatchling #758
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.
Description
This PR switches the build system backend from
setuptools
tohatchling
. It follows the same steps taken in ocs.The same versioning side-effect applies. Versions on installs from source will be slightly different now:
old version format:
0.5.0+14.gc4b73f75
new version format:
0.5.0.post1.dev14+gc4b73f75
I also added and organized some of the dependencies across the
pyproject.toml
andrequirements.txt
files.Motivation and Context
See simonsobs/ocs#403.
How Has This Been Tested?
I have built the package and inspected the resulting sdist. I also ran tests against an installation from the built wheel. This required manual installation of the dependencies not available on PyPI, but after that tests ran mostly fine. I did experience a hanging test related to an SNMP agent, but I was unable to reproduce. We'll see how the tests in the CI go.
Types of changes
Checklist: