Uh oh!
There was an error while loading. Please reload this page.
bpo-33346: Allow async comprehensions inside implicit async comprehensions. - #6766
Conversation
9f24c24 to
0b36223Compare
gvanrossum
left a comment
There was a problem hiding this comment.
Don't merge this yet. I think we need more discussion about the desired behavior. And we need docs to match.
0b36223 to
63c911bComparepablogsal
commented
Jun 1, 2019
Can we include this in beta1? |
de5d817 to
6039db7Compare6039db7 to
f3beb18Comparepablogsal
commented
Jul 13, 2021
I have updated the PR to match the main branch and I am landing this as the discussion in bpo has been quiet for several years and everyone seems to be on the same page. @serhiy-storchaka, Дякую за чудову роботу! 😃 |
serhiy-storchaka
commented
Jul 14, 2021
Wow! |
Summary: In cinder 3.8 we unintentionally allowed async comprehensions to nest inside non-async ones, due to comprehension inlining. When we ported comprehension inlining to 3.10, we closed this hole for better fidelity to upstream compiler behavior, but that means we have to fix the places in IGSRV that now break this rule. And this doesn't seem worth it considering the restriction is lifted in Python 3.11 anyway: python/cpython#6766 This diff just restores the 3.8 behavior of comprehension inlining allowing async comprehensions nested inside non-async ones. Reviewed By: itamaro Differential Revision: D39825885 fbshipit-source-id: bd2f27a
iritkatriel
commented
Jul 2, 2024
I noticed that no tests fail if I comment out this line: Line 5785 in 0898354 and I bisected it to this PR. (1) Does this make sense? |
iritkatriel
commented
Jul 2, 2024
I think it's fine because this PR added in symtable.c code that propagates the value of |
https://bugs.python.org/issue33346