使用asyncio正常关闭，内部任务未取消

最新推荐文章于 2022-03-27 18:28:15 发布

原创最新推荐文章于 2022-03-27 18:28:15 发布 · 5.1k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#使用asyncio正常关闭，内部任务未取消

后端专栏收录该内容

75 篇文章

订阅专栏

本文详细探讨了在使用Telethon库时遇到的异步任务被销毁但仍在等待的问题，具体表现为在断开与Telegram服务器连接时，未正确取消_recv_loop、_ping_loop和_state_loop等异步循环任务，导致错误信息提示。文章提供了Python3.6.4和Telethon-aio0.18.3版本下解决问题的方法，通过在断开连接函数中明确取消这些任务来避免错误。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

ERROR:asyncio:Task was destroyed but it is pending!
task: <Task pending coro=<TelegramBareClient._recv_loop_impl() running at /usr/lib/python3.6/site-packages/telethon/telegram_bare_client.py:630> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7ff0702814f8>()]>>
ERROR:asyncio:Task was destroyed but it is pending!
task: <Task pending coro=<TelegramBareClient._ping_loop_impl() running at /usr/lib/python3.6/site-packages/telethon/telegram_bare_client.py:593> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7ff0702816d8>()]>>
ERROR:asyncio:Task was destroyed but it is pending!
task: <Task pending coro=<TelegramBareClient._state_loop_impl() running at /usr/lib/python3.6/site-packages/telethon/telegram_bare_client.py:598> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7ff070281138>()]>>
解决方式 Versions: Python 3.6.4, Telethon-aio 0.18.3
def disconnect(self):
    """Disconnects from the Telegram server"""
    ...
    if self._recv_loop:
        self._recv_loop.cancel()
    if self._ping_loop:
        self._ping_loop.cancel()
    if self._state_loop:
        self._state_loop.cancel()
        这些任务都存储在TelegramBareClient实例作为_recv_loop，_ping_loop并_state_loop在启动过程中，但不取消断开连接。