Skip to content

[3.10] bpo-45924: Fix asyncio incorrect traceback when future's exception is raised multiple times (GH-30274) #94748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 11, 2022

Conversation

miss-islington
Copy link
Contributor

(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>
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Status check is done, and it's a success ✅ .

@kumaraditya303 kumaraditya303 requested a review from pablogsal July 11, 2022 14:25
@pablogsal pablogsal merged commit aa2142d into python:3.10 Jul 11, 2022
@miss-islington miss-islington deleted the backport-86c1df1-3.10 branch July 11, 2022 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants