[issue32599] Add dtrace hook for PyCFunction_Call

Change by Mateusz Piotrowski <0...@freebsd.org>: -- nosy: +0mp ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32599] Add dtrace hook for PyCFunction_Call

Change by Joannah Nanjekye : -- nosy: +nanjekyejoannah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32599] Add dtrace hook for PyCFunction_Call

Batuhan added the comment: If there are no objections, I can work on a patch. -- nosy: +BTaskaya, christian.heimes, vstinner ___ Python tracker ___

[issue32599] Add dtrace hook for PyCFunction_Call

Change by Pablo Galindo Salgado : -- type: performance -> enhancement ___ Python tracker ___

[issue32599] Add dtrace hook for PyCFunction_Call

New submission from Frank Ch. Eigler : Similar to https://bugs.python.org/issue31574, it would be useful the the interpreter allowed a tracing tool to hook the PyCFunction_Call() site, maybe via the C_TRACE() macro, kind of how it already does in _PyEval_EvalFrameDefault().