Issue 13231: sys.settrace - document 'some other code blocks' for 'call' event type (original) (raw)

Issue13231

Created on 2011-10-20 07:40 by techtonik, last changed 2022-04-11 14:57 by admin.

Messages (2)
msg146009 - (view)	Author: anatoly techtonik (techtonik)	Date: 2011-10-20 07:40
http://docs.python.org/library/sys.html#sys.settrace While writing settrace function you need to know what kind of data is expected and how to get more information about it. Current documentation for sys.settrace doesn't give too much answers. To improve that situation at least with 'call' event: 1. Link 'frame' to the middle of table on inspect module page [1] 2. List all possible 'code blocks' for 'call' event (I know there is module in addition to function) 3. Provide example how to extract popular data for corresponding 'code block' (name for functions, name for modules, name for classes/methods, relative file path, line no, how to detect labmbda function) in a safe manner (inspect page contains some FUD about memory usage) 1. http://docs.python.org/library/inspect#types-and-members
msg221972 - (view)	Author: Mark Lawrence (BreamoreBoy) *	Date: 2014-06-30 18:15
I find this request excessive. The first sentence for sys.settrace states "Set the system’s trace function, which allows you to implement a Python source code debugger in Python". I suspect that anyone wanting to write a debugger would know the Python and its documentation better than the back of their hand. So I say close as "won't fix" but I wouldn't argue if anyone disagreed and wanted to provide a patch.