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 petr.viktorin
Recipients Anthony Sottile, Mark.Shannon, gvanrossum, nedbat, pablogsal, petr.viktorin
Date 2021-04-27.12:53:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619528027.61.0.752124751708.issue43933@roundup.psfhosted.org>
In-reply-to
Content
Please don't lose the big picture here.
Previously, the reported line number was *somewhere close* to the currently executing code. That's typically all I need from a traceback: the fix for a bug often needs to go a few lines above/below where it's reported.

If, in an effort to make line numbers *exact*, we determine that there's no good line number to report and use -1 or None, we're introducing a regression.


> We could give it the line number of the `with` keyword, but that might break coverage and profiling tools.

That sounds like a reasonable idea, despite the drawback. As we can see from the report, *any* change will probably break *some* tools.
History
Date User Action Args
2021-04-27 12:53:47petr.viktorinsetrecipients: + petr.viktorin, gvanrossum, nedbat, Mark.Shannon, Anthony Sottile, pablogsal
2021-04-27 12:53:47petr.viktorinsetmessageid: <1619528027.61.0.752124751708.issue43933@roundup.psfhosted.org>
2021-04-27 12:53:47petr.viktorinlinkissue43933 messages
2021-04-27 12:53:47petr.viktorincreate