8000 bpo-3530: Add advice on when to correctly use fix_missing_locations i… · python/cpython@ef0af30 · GitHub
[go: up one dir, main page]

Skip to content

Commit ef0af30

Browse files
bpo-3530: Add advice on when to correctly use fix_missing_locations in the AST docs (GH-17172)
Co-authored-by: Pablo Galindo <Pablogsal@gmail.com> (cherry picked from commit 6680f4a) Co-authored-by: Batuhan Taşkaya <47358913+isidentical@users.noreply.github.com>
1 parent 3043ec7 commit ef0af30

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

Doc/library/ast.rst

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -300,7 +300,7 @@ and classes for traversing abstract syntax trees:
300300
class RewriteName(NodeTransformer):
301301

302302
def visit_Name(self, node):
303-
return copy_location(Subscript(
303+
return Subscript(
304304
value=Name(id='data', ctx=Load()),
305305
slice=Index(value=Constant(value=node.id)),
306306
ctx=node.ctx
@@ -314,6 +314,14 @@ and classes for traversing abstract syntax trees:
314314
statement nodes), the visitor may also return a list of nodes rather than
315315
just a single node.
316316

317+
If :class:`NodeTransformer` introduces new nodes (that weren't part of
318+
original tree) without giving them location information (such as
319+
:attr:`lineno`), :func:`fix_missing_locations` should be called with
320+
the new sub-tree to recalculate the location information::
321+
322+
tree = ast.parse('foo', mode='eval')
323+
new_tree = fix_missing_locations(RewriteName().visit(tree))
324+
317325
Usually you use the transformer like this::
318326

319327
node = YourTransformer().visit(node)
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
In the :mod:`ast` module documentation, fix a misleading ``NodeTransformer`` example and add
2+
advice on when to use the ``fix_missing_locations`` function.

0 commit comments

Comments
 (0)
0