Generator `yield`s counted as primitive calls by cProfile
Open
Nobody has claimed this yet.
3.10
3.11
3.12
topic-profiling
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42551 |
|---|---|
| Nosy | @msuozzo |
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 2020-12-03.04:29:39.676>
labels = ['type-bug', '3.8', '3.9', '3.10', 'expert-C-API', '3.7']
title = 'Generator `yield`s counted as primitive calls by cProfile'
updated_at = <Date 2020-12-14.21:52:21.585>
user = 'https://github.com/msuozzo'
bugs.python.org fields:
activity = <Date 2020-12-14.21:52:21.585>
actor = 'matthew.suozzo'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2020-12-03.04:29:39.676>
creator = 'matthew.suozzo'
dependencies = []
files = []
hgrepos = []
issue_num = 42551
keywords = []
message_count = 2.0
messages = ['382373', '383007']
nosy_count = 1.0
nosy_names = ['matthew.suozzo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42551'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
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 reproducing the cProfile behavior for a generator containing yield and compare its primitive-call count with the expected result. The issue names no implementation file or test; inspect the cProfile and C API profiling paths, then add coverage showing that generator yields are not counted as primitive calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100