Sujet : sys.call_tracing
De : rob.cliffe (at) *nospam* btinternet.com (Rob Cliffe)
Groupes : comp.lang.pythonDate : 31. Jan 2025, 01:38:38
Autres entêtes
Message-ID : <mailman.95.1738284090.2912.python-list@python.org>
References : 1
User-Agent : Mozilla Thunderbird
From the documentation on the sys module at
https://docs.python.org/3/library/sys.html:
sys.call_tracing(/func/, /args/)
Call |func(*args)|, while tracing is enabled. The tracing state is saved, and restored afterwards. This is intended to be called from a debugger from a checkpoint, to recursively debug or profile some other code.
Tracing is suspended while calling a tracing function set by |settrace()| <
https://docs.python.org/3/library/sys.html#sys.settrace> or |setprofile()| <
https://docs.python.org/3/library/sys.html#sys.setprofile> to avoid infinite recursion. |call_tracing()| enables explicit recursion of the tracing function.
Is there any reason it doesn't support
sys.call_tracing(/func/, /args/, kargs)
to call
func(*args, **kargs)
?
Best wishes
Rob Cliffe