PEP 489 Compatibility
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
Inspired by https://github.com/PyO3/pyo3/pull/2269#issuecomment-1087901951, this is an issue to track all of the places which we know need to change for full PEP 489 compatibility (draft implementation in #2245).
The latest documentation about supporting isolated extensions can be found at https://docs.python.org/3.14/howto/isolating-extensions.html
- Rust statics -
#[pyclass]type objects, most implementations ofPyTypeInfo,intern!
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 with the draft implementation in #2245 and the Python documentation on isolating extensions linked in this issue. Review the listed Rust statics, including #[pyclass] type objects, PyTypeInfo implementations, and intern!, then identify the remaining changes needed for full PEP 489 compatibility. Done means the known compatibility gaps are addressed across these areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100