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 pablogsal
Recipients Mark.Shannon, pablogsal
Date 2021-04-27.10:58:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If we could include column offsets from the AST nodes for every bytecode instructions we could leverage these to offer much better tracebacks and a lot more information to debuggers and similar tools. For instance, in an expression such as:


where one of these elements is None, we could tell exactly what of these pieces is the actual None and we could do some cool highlighting on tracebacks.

Similarly, coverage tools and debuggers could also make this distinction and therefore could offer reports with more granularity.

The cost is not 0: it would be two integers per bytecode instruction, but I think it may be worth the effort.
Date User Action Args
2021-04-27 10:58:38pablogsalsetrecipients: + pablogsal, Mark.Shannon
2021-04-27 10:58:38pablogsalsetmessageid: <>
2021-04-27 10:58:38pablogsallinkissue43950 messages
2021-04-27 10:58:38pablogsalcreate