Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #197223

sys.call_tracing

From Rob Cliffe <rob.cliffe@btinternet.com>
Newsgroups comp.lang.python
Subject sys.call_tracing
Date 2025-01-31 00:38 +0000
Message-ID <mailman.95.1738284090.2912.python-list@python.org> (permalink)
References <a5f32320-e41a-4991-9ffc-89ee06e3df69@btinternet.com>

Show all headers | View raw


 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

Back to comp.lang.python | Previous | Next | Find similar


Thread

sys.call_tracing Rob Cliffe <rob.cliffe@btinternet.com> - 2025-01-31 00:38 +0000

csiph-web