Expose PyErr_ChainExceptions in the stable API
Open
Nobody has claimed this yet.
topic-C-API
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44938 |
|---|---|
| Nosy | @gpshead, @cjerdonek, @serhiy-storchaka, @pablogsal |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-08-17.17:44:23.749>
labels = ['expert-C-API', 'type-feature', '3.11']
title = 'Expose PyErr_ChainExceptions in the stable API'
updated_at = <Date 2021-12-10.19:07:14.668>
user = 'https://github.com/pablogsal'
bugs.python.org fields:
activity = <Date 2021-12-10.19:07:14.668>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2021-08-17.17:44:23.749>
creator = 'pablogsal'
dependencies = []
files = []
hgrepos = []
issue_num = 44938
keywords = ['patch']
message_count = 6.0
messages = ['399777', '399820', '399835', '400101', '400107', '408245']
nosy_count = 4.0
nosy_names = ['gregory.p.smith', 'chris.jerdonek', 'serhiy.storchaka', 'pablogsal']
pr_nums = ['27799']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44938'
versions = ['Python 3.11']
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 PR #27799 and the CPython C API context for PyErr_ChainExceptions first. Confirm how the function should be exposed in the stable API and verify that the finished change matches the Python 3.11 scope; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100