New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sys.settrace - document 'some other code blocks' for 'call' event type #57440
Comments
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:
|
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. |
I can't say that I know documentation better than the back of my hand, but I am writing a tracing tool right now. I've dug around in the depths of Python's codebase before, but documentation exists so that I don't have to break my back looking over a dozen other pages. I would have greatly appreciated more information about the possible code blocks for call, and it would have been tremendously helpful to have information about how to determine what kind of code block is currently being executed. As it stands, I need to differentiate between a class definition being executed and a function definition being executed, and I see nothing in the docs or my experiments that can help me. It seems to me that the settrace docs could benefit from being expanded a little? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: