Calls to C functions using `.__call__` don't get sent to profiler.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- compilers, observability-sre
Research direction
Start by reproducing the reported behavior for calls to C functions through .__call__ under the profiler, using the issue's Python 2.7 and 3.7 scope as context. The work is done when those calls are consistently delivered to the profiler and the relevant behavior is covered by a regression test.
Written by the indexing model from the issue text.
Description
| BPO | 30990 |
|---|---|
| Nosy | @pppery |
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 2017-07-22.12:50:31.546>
labels = ['interpreter-core', 'type-bug', 'library', '3.7']
title = "Calls to C functions using `.__call__` don't get sent to profiler."
updated_at = <Date 2017-07-22.12:50:31.546>
user = 'https://github.com/pppery'
bugs.python.org fields:
activity = <Date 2017-07-22.12:50:31.546>
actor = 'ppperry'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Library (Lib)']
creation = <Date 2017-07-22.12:50:31.546>
creator = 'ppperry'
dependencies = []
files = []
hgrepos = []
issue_num = 30990
keywords = []
message_count = 1.0
messages = ['298847']
nosy_count = 1.0
nosy_names = ['ppperry']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue30990'
versions = ['Python 2.7', 'Python 3.7']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100