Conflict between pragmatic locations and pure spans

The PEG parser produces locations for an AST that span the entire AST node. This is well defined, and has a number of desirable properties such as the span of a node including all its children's spans.

Unfortunately, this does not produce good locations for tracing and debugging, so we transform some locations in the compiler.
This is problematic as it means that tools producing as AST (e.g. pytest) need to second guess what transformations that the compiler will make.

I proposed moving these transformations in the parser in https://github.com/python/cpython/issues/94694, but as @pablogsal points out, this means that tools which consume the AST (e.g. type checkers) need to undo the transformations to get the original spans back.

The core problem is that there are tools that consume the AST produced by the parser, and tools that produce ASTs for consumption by the compiler, and they want subtly different ASTs.

One possible fix for this is to add a keyword argument to compile() to specify whether it should modify the locations. This would allow pytest, etc. to pass location information through compile() unmodified when needed.

Empieza leyendo el issue 94694 y el tratamiento de las ubicaciones de AST por parte del parser/compiler. Compara las necesidades de los consumidores de AST con las de las herramientas que producen ASTs para compile(), y determina después si una opción para conservar las ubicaciones es suficiente. Se considera terminado cuando el comportamiento de las ubicaciones está definido sin que las herramientas tengan que adivinar o deshacer las transformaciones del compiler.