iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

f_lineno, not f_lineo. (#1918) 

I noticed this because the typo even found its way to the [What's new listing in CPython](https://github.com/python/cpython/blame/master/Doc/whatsnew/3.10.rst#L176)
This commit is contained in:
Antti Haapala 2021-04-10 13:44:31 +03:00 committed by GitHub
parent 15ee6f8487
commit b5846bfedd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pep-0626.rst
View File

@ -15,7 +15,7 @@ Abstract
Python should guarantee that when tracing is turned on, "line" tracing events are generated for *all* lines of code executed and *only* for lines of
code that are executed.
The ``f_lineo`` attribute of frame objects should always contain the expected line number.
The ``f_lineno`` attribute of frame objects should always contain the expected line number.
During frame execution, the expected line number is the line number of source code currently being executed.
After a frame has completed, either by returning or by raising an exception,
the expected line number is the line number of the last line of source that was executed.