The co_lnotab attribute will be deprecated in 3.10 and removed in 3.12.
https://peps.python.org/pep-0626/#backwards-compatibility
It was documented as deprecated in 3.10 and to-be-removed in 3.12: https://docs.python.org/3/whatsnew/3.10.html#pep-626-precise-line-numbers-for-debugging-and-other-tools
Original issue: #86412
Right now CPython does not use co_lnotab in its source code.
But, there are two mentions of it:
- In
gdb:
|
set $__sz = ((PyVarObject *)$__co->co_lnotab)->ob_size/2 |
|
set $__p = (unsigned char *)((PyBytesObject *)$__co->co_lnotab)->ob_sval |
And I have no idea how it works! Some weird mix of C and some kind of a DSL / scripting language
- In
clinic.test:
|
co_lnotab: PyBytesObject(c_default="(PyBytesObject *)self->co_lnotab") = None |
But, this is just a string-based test. So, I think it can stay there
If that's fine - I would like to do the honours.
CC @markshannon
Linked PRs
https://peps.python.org/pep-0626/#backwards-compatibility
It was documented as deprecated in 3.10 and to-be-removed in 3.12: https://docs.python.org/3/whatsnew/3.10.html#pep-626-precise-line-numbers-for-debugging-and-other-tools
Original issue: #86412
Right now CPython does not use
co_lnotabin its source code.But, there are two mentions of it:
gdb:cpython/Misc/gdbinit
Lines 60 to 61 in 6ef6915
clinic.test:cpython/Lib/test/clinic.test
Line 3575 in 6ef6915
If that's fine - I would like to do the honours.
CC @markshannon
Linked PRs
co_lnotabfrom code objects as per PEP 626 #101866