Variable sized Python objects become fully opaque in abi3t
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
The PyVarObject data structure becomes opaque in abi3t. Unfortunately, there is no limited API functionality to provide access to elements of a PyVarObject.
The relevant functions PyObject_GetItemData() and PyObject_GetItemData_DuringGC() are marked as unstable.
It would be very important to fix this before Python 3.15 goes out, or any extensions using variable sized objects will be stranded.
CPython versions tested on:
3.15, CPython main branch
Operating systems tested on:
Linux
Linked PRs
- gh-148324
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
Review the linked PR gh-148324 and the PyVarObject limited-API entry points named in the report, including PyObject_GetItemData() and PyObject_GetItemData_DuringGC(). Done means variable-sized objects remain usable through abi3t without relying only on unstable functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100