[3.8] bpo-37937: Mention frame.f_trace in sys.settrace docs (GH-15439)#16296
Merged
Merged
Conversation
Mention frame.f_trace in sys.settrace docs, as well as the fact you still need to call `sys.settrace` to enable the tracing machinery before setting `frame.f_trace` will have any effect. (cherry picked from commit 9c2682e) Co-authored-by: Ram Rachum <ram@rachum.com>
ncoghlan
approved these changes
Sep 20, 2019
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mention frame.f_trace in sys.settrace docs, as well as the fact you still
need to call
sys.settraceto enable the tracing machinery before settingframe.f_tracewill have any effect.(cherry picked from commit 9c2682e)
Co-authored-by: Ram Rachum ram@rachum.com
https://bugs.python.org/issue37937