[issue22616] Allow connecting AST nodes with corresponding source ranges

Edward K Ream added the comment: On Mon, Jan 14, 2019 at 5:24 AM Ivan Levkivskyi wrote: Adding endline and endcolumn to every ast node will be a big improvement. Edward -- Edward K. Ream:

[issue22616] Allow connecting AST nodes with corresponding source ranges

Ivan Levkivskyi added the comment: Closed as superseded by https://bugs.python.org/issue33416 -- superseder: -> Add endline and endcolumn to every AST node ___ Python tracker

[issue22616] Allow connecting AST nodes with corresponding source ranges

Change by Ivan Levkivskyi : -- nosy: +levkivskyi stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue22616] Allow connecting AST nodes with corresponding source ranges

New submission from Aivar Annamaa: Currently lineno and col_offset attributes in AST nodes have confusing roles. According to documentation they indicate the starting position of node's source text but according to recent developments (#16795) they seem to indicate a position most suitable to

[issue22616] Allow connecting AST nodes with corresponding source ranges

R. David Murray added the comment: If it needs some discussion, perhaps it should be raised on python-ideas first. My reading of #16795 (granted I only skimmed it) was that improving the error messages was a *side effect* of making the position information more accurate (in the context of

[issue22616] Allow connecting AST nodes with corresponding source ranges

Edward K. Ream added the comment: I urge the Python development team to fix this and the related bugs given in the Post Script. The lack of an easy way of associating ast nodes with text ranges in the original sources is arguably the biggest hole in the Python api. These bugs have immediate,

[issue22616] Allow connecting AST nodes with corresponding source ranges

R. David Murray added the comment: The python develop team is a group of volunteers. What you need to do to move this forward is to work on patches (or polishing patches, in the case of issue 16806) for open issues for which there has been no objection, and build a consensus for fixing the

[issue22616] Allow connecting AST nodes with corresponding source ranges

R. David Murray added the comment: OK, reading the followon links just added to issue issue 10769, it seems clear you don't need to advocate for the idea of supporting external tools, there seems to be consensus agreement for that. So now it is down to specific proposals and patches. And