-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Adding generator_stop to compile_future_features #5320
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
Adding generator_stop to compile_future_features #5320
Conversation
5e5a905 to
26c1757
Compare
26c1757 to
888d975
Compare
compiler/codegen/src/compile.rs
Outdated
| | "compile_future_features" => {} | ||
| "generator_stop" => {} |
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.
Does this work?
| | "compile_future_features" => {} | |
| "generator_stop" => {} | |
| | "compile_future_features" | |
| | "generator_stop" => {} |
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.
Oops, my autoformatter led to that silly mistake. I also somehow introduced compile_future_features there!
To answer your question: it seems to work.
I did a quick check on the Python interpreter and the import succeeds. The module also looks okay via dir() inspection.
Anyhow, I will fix it. Thanks for pointing that out.
7b94f23 to
28f407b
Compare
youknowone
left a comment
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.
Thank you for contributing! Your patch also fixed a test in test_contextlib. Could you also update the test? Removing @unittest.expectedFailure will fix the CI failure
As well as some mild formatting.
Fix #4060