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
"__lltrace__" seems to be wrong , "__ltrace__" is correct in Misc/SpecialBuilds.txt #78607
Comments
|
In the Section "LLTRACE" of $(Python3.6-source)/Misc/SpecialBuilds.txt , it describes variable name is "__lltrace__",however it seems to be wrong, "__ltrace__" is correct. Would someone correct this document? |
just curious how did you figure it out? |
|
Content Hi @nojima and thank you for the report. Do you mind doing a PR? If not, I can do it myself if you prefer. |
|
@pablogsal I would love to fix this up |
|
Thanks! |
|
I think it may have been that the documentation was correct, but the code had a typo: The typo was introduced in 2012 in this commit: 3c1e481 I think "lltrace" (the variable names in the C code) is a better abbreviation for "low-level trace". Since this has been around for 10 years, at this point, we could give up and do the low-level tracing if either |
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: