Calls to C functions using `.call` don't get sent to profiler.

Open

#75,173 opened on Jul 22, 2017 1 comment 0 reactions 0 assignees View on GitHub

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
Tech stack: c, python
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

3.7 (EOL) interpreter-core stdlib type-bug

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

Open the contributing 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.

Similar issues

RadioSelectButtonGroup does not render as a button group through bootstrap_field Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

zostera/django-bootstrap4#894 · Opened Sep 21, 2026
[Bug]: control_ui.show_thinking = false does not stop the live reasoning stream, so thinking events and done.reasoning_content still reach the web UI Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

use-agent-os/agent-os#3276 · Opened Sep 21, 2026
Build fails with LTO enabled: conflicting types for z_shared_sw_isr_table between isr_tables.c and sw_isr_table.h Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

zephyrproject-rtos/zephyr#119726 · Opened Sep 21, 2026
[Bug]: redact_sensitive_text does not recognise Discord bot tokens Open

area/auth bug comp/agent P3 platform/discord type/security

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

NousResearch/hermes-agent#117848 · Opened Sep 21, 2026
Windows: hooks treat CLAUDE_PROJECT_DIR (C:/... style) as relative, session summaries written to a doubled path Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

zilliztech/memsearch#759 · Opened Sep 21, 2026

More Python issues

Calls to C functions using `.__call__` don't get sent to profiler.