Python: Switch to maturin for all Python building/development #2345
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.
(based on #2344)After the recent universal2 wheel work I realized how messy our Python setup is:
A big home-grown solution inside a
setup.py
reinventing half of Python package management all over again.There must be something better for it.
There is: maturin.
Tried and trusted in other projects, this tool can take care of most of the build and development hassles of a Python package with UniFFI bindings.
This PR switches our development tooling over to maturin, for both local development and on CI.
And while I was at it I also moved all Python tooling configuration into the one and only
pyproject.toml
.This is not yet ready for merge, because:
Python 3_6 tests
,Python 3_6 tests minimum dependencies
andPython 3_9 tests minimum dependencies
as those tests are gone.