ABI3-like for non-`extension-module`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
Description
I'd like for non-extension-module builds to be able to use newer Python interpreters, similar to how the ab3 feature set works. However, the feature description says it's "used when building Python extension modules" so it won't do anything for me.
My use case
I'd like to build an app with Rust <-> Python, but Rust first instead of Python first. I actually need Python 3.7 support, but I'd also like for users to be able to choose a newer Python version if they want. I've figured out how to set different Python interpreters by setting PATH before the interpreter is initialized, but I'd like it to be able to optionally use any newer Python version even if that means that I need every Python interpreter I just want one single binary for app user convenience.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing ab3 feature description and behavior with the non-extension-module build path; the issue does not name specific files or tests. Determine how a Rust-first application could support Python 3.7 while optionally running with newer interpreters, then document the compatibility constraints and verify the selected interpreter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100