[issue34349] asyncio.wait should accept generator of tasks as first argument

Yury Selivanov added the comment: Since we're deprecating generator-based coroutines anyways, I too think that the check can be relaxed. -- versions: +Python 3.8 -Python 3.7 ___ Python tracker

[issue34349] asyncio.wait should accept generator of tasks as first argument

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34349] asyncio.wait should accept generator of tasks as first argument

Change by epiphyte : -- nosy: +epiphyte ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34349] asyncio.wait should accept generator of tasks as first argument

New submission from Nic Watson : Currently, passing a generator of coroutines or futures as the first parameter of asyncio.wait raises a TypeError. This is in conflict with the documentation calling the first parameter a "sequence". Line in question.