Tracing: c_return doesn't report the result
Open
Nobody has claimed this yet.
3.10
3.11
topic-C-API
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 46781 |
|---|---|
| Nosy | @smurfix, @markshannon |
| 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 2022-02-17.18:08:22.285>
labels = ['expert-C-API', 'type-feature', '3.10', '3.11']
title = "Tracing: c_return doesn't report the result"
updated_at = <Date 2022-03-04.12:30:19.902>
user = 'https://github.com/smurfix'
bugs.python.org fields:
activity = <Date 2022-03-04.12:30:19.902>
actor = 'Mark.Shannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2022-02-17.18:08:22.285>
creator = 'smurfix'
dependencies = []
files = []
hgrepos = []
issue_num = 46781
keywords = ['patch']
message_count = 4.0
messages = ['413421', '413444', '413454', '414522']
nosy_count = 2.0
nosy_names = ['smurfix', 'Mark.Shannon']
pr_nums = ['31393']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46781'
versions = ['Python 3.10', '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
Start with the C API tracing implementation for c_return and review PR #31393, which is the existing work on this issue. Determine the expected result-reporting behavior from the issue and PR discussion, then verify that c_return reports the result consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- backend-api-design, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100