bpo-41218: Only mark async code with CO_COROUTINE.#21357
Conversation
|
@Carreau Could you add also a NEWS entry? |
3.8.3 had a regression where compiling with ast.PyCF_ALLOW_TOP_LEVEL_AWAIT woudl agressively mark things are coroutine even if there were not.
|
Rebased, NEWS file added and suggestion applied. |
How could it not? |
|
@ambv: Please replace |
|
Sorry @Carreau and @ambv, I had trouble checking out the |
|
GH-21361 is a backport of this pull request to the 3.8 branch. |
|
@pablogsal, approving first, reviewing later is a new style for me ;-) |
3.8.3 had a regression where compiling with ast.PyCF_ALLOW_TOP_LEVEL_AWAIT woudl agressively mark things are coroutine even if there were not. (cherry picked from commit bd46174) Co-authored-by: Matthias Bussonnier <bussonniermatthias@gmail.com>
I forgot to add a couple of suggestions to clean the test suite, I will submit a followup :) |
|
GH-21362 is a backport of this pull request to the 3.9 branch. |
3.8.3 had a regression where compiling with ast.PyCF_ALLOW_TOP_LEVEL_AWAIT woudl agressively mark things are coroutine even if there were not. (cherry picked from commit bd46174) Co-authored-by: Matthias Bussonnier <bussonniermatthias@gmail.com>
…H-21362) 3.8.3 had a regression where compiling with ast.PyCF_ALLOW_TOP_LEVEL_AWAIT woudl agressively mark things are coroutine even if there were not. (cherry picked from commit bd46174) Co-authored-by: Matthias Bussonnier <bussonniermatthias@gmail.com> Co-authored-by: Matthias Bussonnier <bussonniermatthias@gmail.com>
3.8.3 had a regression where compiling with
ast.PyCF_ALLOW_TOP_LEVEL_AWAIT would agressively mark things are
coroutine even if there were not.
https://bugs.python.org/issue41218