Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
pppery mannequin opened this issue Jul 22, 2017 · 1 comment
Open

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

pppery mannequin opened this issue Jul 22, 2017 · 1 comment
Labels
3.7 (EOL) end of life interpreter-core (Objects, Python, Grammar, and Parser dirs) stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error

Comments

@pppery
Copy link
Mannequin

pppery mannequin commented Jul 22, 2017

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']
@pppery
Copy link
Mannequin Author

pppery mannequin commented Jul 22, 2017

If you create a file called inputtest.py with the contents input.__call__(), and run the built-in profile module on it, it doesn't notice the call to input, and produces a report not including that call.
4 function calls in 0.000 seconds

Ordered by: standard name

ncalls tottime percall cumtime percall filename:lineno(function)
1 0.000 0.000 0.000 0.000 :0(exec)
1 0.000 0.000 0.000 0.000 :0(setprofile)
1 0.000 0.000 0.000 0.000 inputtest.py:1(<module>)
1 0.000 0.000 0.000 0.000 profile:0(<code object <module> at 0x00000000029880C0, file "inputtest.py", line 1>)
0 0.000 0.000 profile:0(profiler)

@pppery pppery mannequin added 3.7 (EOL) end of life interpreter-core (Objects, Python, Grammar, and Parser dirs) stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error labels Jul 22, 2017
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.7 (EOL) end of life interpreter-core (Objects, Python, Grammar, and Parser dirs) stdlib Python modules in the Lib dir type-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants