Repository navigation
Conversation
pyo3 0.27 refuses to build for Python 3.15 ("the configured Python
version (3.15) is newer than PyO3's maximum supported version (3.14)").
With no 3.15 wheel on PyPI, installs on 3.15 build from source and
fail, which blocks bbot's Python 3.15 support (bbot#3474).
- pyo3 0.27 -> 0.30, no code changes needed
- cargo update for all other semver-compatible crates
- uv lock --upgrade for dev tools (pytest 9.1, ruff 0.17, pytest-cov 7.1)
- add 3.15 to the CI test matrix and classifiers
rand stays on 0.8: the 0.10 API rename would conflict with #64's tests.
RadixTarget Benchmark Results100000 networks per table, 100000 lookups, median of 5 runs (seed 1337).
Change is in time taken: negative is faster. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #103 +/- ##
===================================
Coverage 100% 100%
===================================
Files 3 3
Lines 604 605 +1
===================================
+ Hits 604 605 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
3.9 is end-of-life and 3.10 reaches end-of-life this month; bbot is dropping 3.10 as well (bbot#3474). requires-python is now >=3.11, and 3.9/3.10 are removed from the CI matrix, classifiers and README badge.
liquidsec
changed the title
This was referenced Oct 19, 2026
Merged
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
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.
Unblocks bbot's Python 3.15 PR (blacklanternsecurity/bbot#3474). Its
test (3.15)job fails while installing radixtarget:There's no 3.15 wheel on PyPI, so pip builds radixtarget from source, and pyo3 0.27 doesn't support 3.15.
Changes
pyo30.27 → 0.30. The bindings compile unchanged, with no new clippy warnings.cargo updatefor every other semver-compatible crate (ipnet2.12,icu_*2.3,libc,proc-macro2, …).uv lock --upgradefor dev tools: pytest 9.1, ruff 0.17, pytest-cov 7.1, coverage 7.16. Lockfile format unchanged (revision 3).requires-pythonis now>=3.11, and the CI matrix, classifiers, README badge anduv.lockare updated to match.Verified locally
cargo fmt,clippy -D warnings,cargo test,pytestandruffall pass.Not in this PR
rand0.8 → 0.10 (test-only): its API renames would conflict with the differential test in Faster IP Tree #64. Better done after Faster IP Tree #64 lands.To actually unblock bbot, this has to ship in a release: a version bump, then
dev→stableso the publish pipeline builds 3.15 wheels.