bpo-45924: Fix asyncio incorrect traceback when future's exception is raised multiple times#30274
Conversation
5ac4c8d to
9f9e469
Compare
|
BTW, GitHub does not play well with force pushes (contrary to GitLab). If you use Note: if there has been no comments on a PR, there is of course no harm in force-pushing. |
eeb4c56 to
adb12a7
Compare
… raised multiple times
adb12a7 to
15a9cfe
Compare
|
Fixed.
|
|
New test is a little harder to read but much stablier |
It was a recent github action which was broken, should be fixed now as I merged with main. |
iritkatriel
left a comment
There was a problem hiding this comment.
I'd put the subclasses right after the base class, like so.
Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
|
Thanks for the reviews! I have addressed all the review comments and now I would like to see this merged and make anymore improvement if required in separate PRs. Perfect is the enemy of good! |
I checked again and confirmed that both versions are tested now. I think this can be merged now.
This is true with respect to many things (like homework - it doesn't really matter whether you graduate with a GPA of 85% or 90%). But when it comes to complex software you get "good" by aiming for "perfect". |
|
Thanks @kumaraditya303 for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
|
GH-94747 is a backport of this pull request to the 3.11 branch. |
|
GH-94748 is a backport of this pull request to the 3.10 branch. |
… raised multiple times (pythonGH-30274) (cherry picked from commit 86c1df1) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
… raised multiple times (pythonGH-30274) (cherry picked from commit 86c1df1) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
https://bugs.python.org/issue45924