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

本文详细探讨了在使用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在启动过程中,但不取消断开连接。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值