Repository navigation
Inconsistent behavior for sys.monitoring.events.CALL #116626
Description
Bug report
Bug description:
According to the docs, CALL event should be emitted as long as there's a function call in Python code. However, CALL_FUNCTION_EX does it differently - it only emits the event when it's a call to C function. So monitoring the following code produce different results:
def f(a, b):
return a + b
f(1, 2) # Emits CALL event
args = (1, 2)
f(*args) # Does NOT emit CALL eventI think we should just fix CALL_FUNCTION_EX to make it work the same as the other CALL instructions.
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Activity
markshannon commentedon Mar 12, 2024
Yes,
CALL_FUNCTION_EXshould behave exactly like otherCALLinstructions.gh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL_FUNCTION_EX` (…
[3.12] pythongh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL…
[3.12] gh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL_FUNCT…
hugovk commentedon Mar 15, 2024
Closing because the PR has been merged and backported. Please re-open if there's more needed here.
pythongh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL_FUNCTI…
pythongh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL_FUNCTI…
pythongh-116626: Emit `CALL` events for all `INSTRUMENTED_CALL_FUNCTI…