build!: drop support for Python v3.7 and v3.8 #128
Merged
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.
Breaking Changes!
Python 3.7 and v3.8 have been dead for over a year now. v3.9 is slated for death in a few weeks. These changes still maintains support for v3.9 (or newer). I held out as long as I could, but this was inevitable.
cibuildwheelto v3 andpybind11to v3. This allows building/supporting Python v3.14.Tip
The new craze in Python is free-threaded builds. Meaning, v3.14t (note the suffixed
tin the python version) boasts true parallelism because it gets rid of the old GIL (mechanism that locks the python runtime to 1 thread).We shouldn't need to do anything on our end because RF24 uses mutex locks for hardware access (to SPI buses, GPIO pins are guarded by the Linux Kernel's char-dev API). We only needed to bump the build tools (pybind11 and cibuildwheel) to support the newer CPython C API.