This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author levkivskyi
Recipients gvanrossum, levkivskyi, lukasz.langa, serhiy.storchaka, vstinner
Date 2018-05-03.10:15:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525342525.55.0.682650639539.issue33416@psf.upfronthosting.co.za>
In-reply-to
Content
Some Python tools (in particular I am interested in type checkers) will benefit from knowing where a given expression ends to indicate/highlight location of an error in the source code. Other tools and IDEs may have also some other benefits. Currently such tools need to use some hacks and/or custom parser to find the end line and end column of an expression, while it would be more straightforward to just add this information to every AST node by CPythons own parser.

This will increase memory usage, but expectation is that this effect will be minor.

What do you think?
History
Date User Action Args
2018-05-03 10:15:25levkivskyisetrecipients: + levkivskyi, gvanrossum, vstinner, lukasz.langa, serhiy.storchaka
2018-05-03 10:15:25levkivskyisetmessageid: <1525342525.55.0.682650639539.issue33416@psf.upfronthosting.co.za>
2018-05-03 10:15:25levkivskyilinkissue33416 messages
2018-05-03 10:15:25levkivskyicreate