You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"__lltrace__" seems to be wrong , "__ltrace__" is correct in Misc/SpecialBuilds.txt #78607
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:
assignee=Noneclosed_at=<Date2018-08-25.02:08:01.544>created_at=<Date2018-08-18.05:35:11.033>labels= ['3.8', 'type-bug', '3.7', 'docs']
title='"__lltrace__" seems to be wrong , "__ltrace__" is correct in Misc/SpecialBuilds.txt'updated_at=<Date2018-08-25.02:15:59.350>user='https://bugs.python.org/NojimaTakahide'
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?
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 __ltrace__ or __lltrace__ is present in the global namespace.
Activity
NojimaTakahide commentedon Aug 18, 2018
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?
danishprakash commentedon Aug 19, 2018
just curious how did you figure it out?
pablogsal commentedon Aug 19, 2018
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.
danishprakash commentedon Aug 19, 2018
@pablogsal I would love to fix this up
Mariatta commentedon Aug 25, 2018
New changeset 09efe49 by Mariatta (Danish Prakash) in branch 'master':
bpo-34426: fix typo (lltrace -> __ltrace__) (GH-8822)
09efe49
Mariatta commentedon Aug 25, 2018
Thanks!
miss-islington commentedon Aug 25, 2018
New changeset 0dc75f0 by Miss Islington (bot) in branch '3.7':
bpo-34426: fix typo (lltrace -> __ltrace__) (GH-8822)
0dc75f0
Mariatta commentedon Aug 25, 2018
New changeset b26fcd6 by Mariatta (Miss Islington (bot)) in branch '3.6':
bpo-34426: fix typo (lltrace -> __ltrace__) (GH-8822)
b26fcd6
sweeneyde commentedon Apr 15, 2022
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
__ltrace__or__lltrace__is present in the global namespace.gh-78607: Replace __ltrace__ with __lltrace__ (GH-91619)