-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-101326: Fix regression when passing None to FutureIter.throw #101327
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
Conversation
hauntsaninja
commented
Jan 25, 2023
•
edited by bedevere-bot
Loading
edited by bedevere-bot
- Issue: Regression in Python 3.11 when explicitly passing None to FutureIter.throw #101326
The windows test failure seems unrelated. |
Misc/NEWS.d/next/Library/2023-01-25-18-07-20.gh-issue-101326.KL4SFv.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Sebastian Rittau <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that definitely happened by accident.
The update to the news entry isn't right. There is also a regression when passing None to the second argument, it's just the error for the third argument happens first. |
Misc/NEWS.d/next/Library/2023-01-25-18-07-20.gh-issue-101326.KL4SFv.rst
Outdated
Show resolved
Hide resolved
Thanks @hauntsaninja for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, @hauntsaninja, I could not cleanly backport this to |
GH-101328 is a backport of this pull request to the 3.11 branch. |
…r.throw (pythonGH-101327). (cherry picked from commit a178ba8) Co-authored-by: Shantanu <[email protected]>
GH-101327) (#101328) (cherry picked from commit a178ba8) Co-authored-by: Shantanu <[email protected]>
|
|