[issue12953] Function calls missing from profiler output

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.9 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list m

[issue12953] Function calls missing from profiler output

Terry J. Reedy added the comment: Range and most of the itertools functions are exposed at the Python level as iterator classes. (But since C does not have classes, they must be C-level functions!) The int 'class' is also not profiled. I think this is wrong behavior. Int and range used to be

[issue12953] Function calls missing from profiler output

Hagen Fürstenau added the comment: It happens for other C functions as well, e.g. itertools.permutations: >>> profile.run('itertools.permutations(range(10), 3)') 4 function calls in 0.000 seconds Ordered by: standard name ncalls tottime percall cumtime percall filename:line

[issue12953] Function calls missing from profiler output

R. David Murray added the comment: I wonder if it has something to do with range returning a special type? range and len are very different things under the hood. -- nosy: +r.david.murray ___ Python tracker

[issue12953] Function calls missing from profiler output

Terry J. Reedy added the comment: Thanks for the report, which I verified on 3.2.2, Win7. When reporting a bug, please give a minimal example of code showing the bug, and the buggy output. I presume you mean something like the following (slightly edited): >>> profile.run('for i in range(10):

[issue12953] Function calls missing from profiler output

New submission from Hagen Fürstenau : I noticed that some function calls don't get reported by profile/cProfile. For example, 'len' works fine, but calls to 'range' or functions in 'itertools' don't show up. Is this a known limitation? I remember that there was a bug in profiling C-functions w