-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Incorrect tracing of "if" inside async-for #93061
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
Labels
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-bug
An unexpected behavior, bug, or error
Comments
This was referenced May 21, 2022
markshannon
pushed a commit
that referenced
this issue
May 23, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 23, 2022
…ythonGH-93062) (cherry picked from commit a458be3) Co-authored-by: Dennis Sweeney <[email protected]>
sweeneyde
added a commit
that referenced
this issue
May 23, 2022
… (GH-93110) (cherry picked from commit a458be3) Co-authored-by: Dennis Sweeney <[email protected]>
sweeneyde
added a commit
that referenced
this issue
May 23, 2022
I think this should be fixed now in 3.10, 3.11, and main, but feel free to re-open if I've missed something. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-bug
An unexpected behavior, bug, or error
Tracing an if-statement in an async-for seems to trace statements that aren't executed. It was correct in 3.9, became wrong in 3.10, and remains wrong in 3.11.
Running this code with 3.11.0b1 gives:
The lines marked with
<<<<
show a break statement being traced when it is not executed.The text was updated successfully, but these errors were encountered: