To create tables for testing dis and such, I'd recommend parsing Python code, modifying the locations on the AST, then generating the code object with compile.

Oh, that's what I was searching for in#123168. Should I amend this PR and use your approach instead?

Yes, make a new PR though as that one was merged.

Actually, modifying the AST does not help because I can't remove some attributes that are expected to exist on the nodes. In particular, I cannot cancel positions (but I can easily change the values of the positions). So I think we need to stick with theco_linetable approach (unless there is something I'm missing?)

I see. You can't set an expression to have no location, because the compiler will just give it one.
FTR, you could test the no columns case by settingnode.end_lineno = node.end_col_offset = -1, and leaving the line number.

I think the test you wrote is fine. There is need to rewrite it.

no columns case by setting node.end_lineno = node.end_col_offset = -1,

Yes, that's what I saw. But I'm not sure whether this is actually a bug or a feature of the compiler (namely, whether the -1 is really meant to indicate "no location").

So I managed to use AST tricks only though I'm not really sure that setting the columns to -1 means that we are deleting the information. I'll remove the artificial constructions in these docs anyway.

Friendly ping@iritkatriel (I'll fix the merge conflicts once I'm back, sorry missed that one)

There's a merge conflict now.

Since I'm on mobile I cannot resolve it but I'll take care of it on Friday (or maybe you can if you have time). Sorry for bothering you!

@iritkatriel Ok, actually thelocations.md file was gone! So I fixed the conflicts. By the way, I put everything under the "Source code locations" section (semantically speaking I think the way we encode integers, the meaning of locations and the short forms are all part of this topic).

Thank you!