Prepare build infrastructure for Rust extension (maturin + PyO3) #1186
Conversation
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
Configure Cargo.toml and pyproject.toml for PyO3 extension. Include a CI workflow for building wheels with maturin for different OS and Python versions.
This was referenced Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds the minimal build infrastructure required to support a Rust-based extension module using
PyO3andmaturin.It is purely preparatory and does not introduce any functional or runtime changes to the existing Python SDK.
Specifically, this PR:
pyproject.tomlas the build entry point, which is required bymaturinand coexists with the existing Python packaging setup.Cargo.tomlto define a Rust crate that will later host the extension module.maturin) to build Python wheels across supported platforms and Python versions.The workflow has been intentionally modified to only build and upload artefacts, and does not publish to PyPI.
This lays the groundwork for follow-up PRs that will incrementally add Rust code and Python-Rust integration, while keeping the current behaviour unchanged.