GeezerVison

A couple doctest failures FYI: https://travis-ci.com/github/python/cpython/jobs/520228793

🤖 New build scheduled with the buildbot fleet by @pablogsal for commit 0673116a6fa30547c1138fd3f96059412d99a979 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

Instead of adding three additional location fields to each instruction, and continually update the equivalent fields in the scope struct, why not change i_lineno to i_ast_node to hold the AST node with the matching location?

Doesn't PEP 657 require that the locations match those of the AST exactly?

Instead of adding three additional location fields to each instruction, and continually update the equivalent fields in the scope struct, why not change i_lineno to i_ast_node to hold the AST node with the matching location?

That would be basically the same because you are modifiying these fields in the compilation and assembler steps. For example:

...
b->b_instr[i].i_lineno = prev_lineno;
...

that means that if we use a i_ast_node pointer all instructions will share the same ast node, so changes to the lineno of one instruction will affect others, which is a big problem. So either we start adding a bunch of macros to get and set to handle the default case a NULL pointer for i_ast_node or we would end copiying the ast node location structure, which is almost exactly what we are doing currently.

Doesn't PEP 657 require that the locations match those of the AST exactly?

No, the PEP just states what is the source of the information, but it doesn't explain how is propagated. So we have some freedom to select from which nodes do we pick the information or to "fix it" if we ever need to.

@isidentical By the way, it seems that there are more places where we are setting lineno = -1 that we didn't update to also account for the new fields

@terryjreedy Adding you as a reviewer as requested. You might not be too interested in this part, it's just exposing the lower level offset data but the tests might give you sort of an idea on how they can be used from Python. The follow up PRs will add the traceback.py changes that you might be more interested in.

🤖 New build scheduled with the buildbot fleet by @isidentical for commit ba64180d3f61ee75b2b624ae2055ec22a2fb27fc 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

Amended the commit message as per Terry's recommendation and rebased #26958 on top of the latest changes, tests for the traceback changes are still passing.