gh-106922: Support multi-line error locations in traceback (attempt 2)#112097
gh-106922: Support multi-line error locations in traceback (attempt 2)#112097pablogsal merged 6 commits into
Conversation
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Sorry, something went wrong.
Sorry, something went wrong.
|
@williamwen42 Seems that there are a bunch of doctests that still fail, can you take a look? |
Sorry, something went wrong.
9d9a510 to
4094c93
Compare
November 17, 2023 19:32
pablogsal
left a comment
There was a problem hiding this comment.
This looks very good. Great work. I made a first pass over the code.
Sorry, something went wrong.
|
@lysnikolaou Can you take a look when you have some time? This is a considerable ammount of code and I think it needs extra eyes |
Sorry, something went wrong.
lysnikolaou
left a comment
There was a problem hiding this comment.
This look very good in general indeed. Thanks @williamwen42! I left some comments, some require further discussion.
Sorry, something went wrong.
4094c93 to
425c874
Compare
November 21, 2023 22:04
|
Will make another pass this week. Thanks for your patience @williamwen42! |
Sorry, something went wrong.
pablogsal
left a comment
There was a problem hiding this comment.
LGTM
This is a fantastic job @williamwen42 thanks a lot for your patience and for following along with us. You rock 🤘
I left a nit comment but after @lysnikolaou takes a look I think we can land it.
A heads up: it's possible that we may require some changes from now to the first beta if some users or core devs find some aspects of this confusing or not very legible, but we can address those once we have more concrete aspects to discuss.
Sorry, something went wrong.
On it. |
Sorry, something went wrong.
lysnikolaou
left a comment
There was a problem hiding this comment.
Let's merge this! Thanks @williamwen42 for doing this. Great work! 🚀
Sorry, something went wrong.
|
Merged! Congratulations @williamwen42! Thanks a lot for your contribution |
Sorry, something went wrong.
…d_lineno` changed in 3.13 (pythonGH-130755) The value taken by `FrameSummary.end_lineno` when passing `end_lineno=None` changed in pythongh-112097. Previously, a `end_lineno` could be specified to be `None` directly but since 939fc6d, passing None makes the constructor use the value of `lineno` instead. (cherry picked from commit c6513f7) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
…nd_lineno` changed in 3.13 (GH-130755) (#130767) gh-128481: indicate that the default value for `FrameSummary.end_lineno` changed in 3.13 (GH-130755) The value taken by `FrameSummary.end_lineno` when passing `end_lineno=None` changed in gh-112097. Previously, a `end_lineno` could be specified to be `None` directly but since 939fc6d, passing None makes the constructor use the value of `lineno` instead. (cherry picked from commit c6513f7) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Attempt 2 at #109589 - the C changes are no longer required, so only python files and tests are touched. Otherwise, the method to output multi-line errors remains unchanged compared to the original PR.