Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
[3.11] GH-100762: Don't call gen.throw() in gen.close(), unless necessary#101316
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
Do we still want to do this? The code looks fine to me... I'm not sure why the tests are failing, but it definitely seems related.
Given 3.13 will be released soon and this is working in 3.12, I don't think it is worth investigating further why this doesn't work. |
Uh oh!
There was an error while loading.Please reload this page.
This a backport of#101013 in principle, although the mechanism for determining when to skip the call to
throw()is different.