Message355443
> Actually, since Andrew also agrees that we need to deprecate passing coroutines to wait(), I'll keep this issue open until we add an actual DeprecationWarning in 3.8.
Since 3.8 has been released and the deprecation notice is in the 3.8 whatsnew document, should we implement the warning in Lib/asyncio/tasks.py? If so, I can open a PR.
> PendingDeprecationWarning
Also, it's not clear to me if this should be a DeprecationWarning or PendingDeprecationWarning. The most recent message from Yury in the issue suggests a PendingDeprecationWarning, but the actual entry in the documentation (https://docs.python.org/3/library/asyncio-task.html?highlight=asyncio%20wait#asyncio.wait) seems like it might imply that it would be a DeprecationWarning:
> Deprecated since version 3.8: If any awaitable in aws is a coroutine, it is automatically scheduled as a Task. Passing coroutines objects to wait() directly is deprecated as it leads to confusing behavior. |
|
Date |
User |
Action |
Args |
2019-10-27 03:00:59 | aeros | set | recipients:
+ aeros, asvetlov, serhiy.storchaka, yselivanov, miss-islington, xtreak |
2019-10-27 03:00:59 | aeros | set | messageid: <1572145259.46.0.803344728284.issue34790@roundup.psfhosted.org> |
2019-10-27 03:00:59 | aeros | link | issue34790 messages |
2019-10-27 03:00:58 | aeros | create | |
|