| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This looks good. Just change the test. |
Sorry, something went wrong.
|
One minor efficiency improvement that could be made is to not call _PyGen_yf(gen) until after the checks for FRAME_CREATED and FRAME_COMPLETED. |
Sorry, something went wrong.
|
Would it be possible / make sense to cherry-pick this change onto 3.12? For pylint / astroid we're seeing ValueError: generator already executing errors since 3.12.0b1. We haven't been able to create a standalone reproducer - which is also the reason I haven't opened a bug report yet. However testing either 3.13.0a2 or 3.12 with this change cherry-picked on top does seem to resolve it as best as I can tell. |
Sorry, something went wrong.
I think so. I'll make a PR. |
Sorry, something went wrong.
|
Thanks @iritkatriel for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
(cherry picked from commit 0db2517) Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
|
GH-115818 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
…GH-111069) (python#115818)" This reverts commit eb4774d.
| Back | FazBrowse Home | New Git URL |
In f02fa64 lines 383-389 were added, with returns that do not decref yf. I think this is ok because yf is always NULL in these cases. Adding the assertions.
Also, the optimization for the case of exception_handler_depth== 1 is not working because op.code is checked instead of op.arg.