async generator bug fixed in 3.8+ and backported to 3.6 but not to 3.7
Hi,
The fix for https://bugs.python.org/issue33786 ("@asynccontextmanager doesn't work well with async generators") was merged in 3.8 and then backported to 3.6. However, it was overlooked to be backported for 3.7 ( https://github.com/python/cpython/pull/7506).
I'm aware that 3.7 is in security fix mode only so I'm not sure there's more to be done, however, given that this is fixed for 3.6, 3.7 is in a weird position still having the bug.
So I just wanted to bring this up in case the fix can still be backported to 3.7.
Matt
If the release manager agrees, this should be a simple call to cherry-picker.
On Tue, Aug 11, 2020 at 13:18 Matthew Einhorn moiein2000@gmail.com wrote:
Hi,
The fix for https://bugs.python.org/issue33786 ("@asynccontextmanager doesn't work well with async generators") was merged in 3.8 and then backported to 3.6. However, it was overlooked to be backported for 3.7 ( https://github.com/python/cpython/pull/7506).
I'm aware that 3.7 is in security fix mode only so I'm not sure there's more to be done, however, given that this is fixed for 3.6, 3.7 is in a weird position still having the bug.
So I just wanted to bring this up in case the fix can still be backported to 3.7.
Matt _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/LW73WSFP... Code of Conduct: http://python.org/psf/codeofconduct/
On Aug 11, 2020, at 16:59, Guido van Rossum guido@python.org wrote:
If the release manager agrees, this should be a simple call to cherry-picker.
On Tue, Aug 11, 2020 at 13:18 Matthew Einhorn moiein2000@gmail.com wrote:
The fix for https://bugs.python.org/issue33786 ("@asynccontextmanager doesn't work well with async generators") was merged in 3.8 and then backported to 3.6. However, it was overlooked to be backported for 3.7 (https://github.com/python/cpython/pull/7506).
I'm aware that 3.7 is in security fix mode only so I'm not sure there's more to be done, however, given that this is fixed for 3.6, 3.7 is in a weird position still having the bug.
So I just wanted to bring this up in case the fix can still be backported to 3.7.
Thanks for bringing this up. I have re-opened bpo-33786 to include the missing 3.7 backport in the next 3.7.x release.
-- Ned Deily nad@python.org -- []
participants (3)
-
Guido van Rossum -
Matthew Einhorn -
Ned Deily