feat: add support for installing pre-built wheels #239
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
emmettbutler
previously approved these changes
Jan 9, 2026
gnufede
previously approved these changes
Jan 9, 2026
brettlangdon
dismissed stale reviews from gnufede and emmettbutler
via
4ada734
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.
This PR adds support for installing the project under test from pre-built wheels instead of editable mode. This is useful for testing with production-like builds, validating wheel packaging, and improving test reproducibility in CI/CD environments.
The feature is available via the
--wheel-pathglobal option orRIOT_WHEEL_PATHenvironment variable, which accepts either a local directory path or a remote URL. When specified, riot uses a two-step installation process (pip download --no-index+pip install) to ensure only wheels from the specified source are used, with no fallback to PyPI. Package names are automatically resolved frompyproject.tomlor theRIOT_PACKAGE_NAMEenvironment variable.Example usage: