Python3.5 Asyncio - 防止任务异常转储到标准输出？

Question

我的程序有一个基于文本的界面（asciimatics 模块），它使用 asyncio 和 discord.py 模块，偶尔当我的 wifi 适配器出现故障时，我会遇到这样的异常：

Task exception was never retrieved
future: <Task finished coro=<WebSocketCommonProtocol.run() done, defined at /home/mike/.local/lib/python3.5/site-packages/websockets/protocol.py:428> exception=ConnectionResetError(104, 'Connection reset by peer')>
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step
    result = coro.throw(exc)
  File "/home/mike/.local/lib/python3.5/site-packages/websockets/protocol.py", line 434, in run
    msg = yield from self.read_message()
  File "/home/mike/.local/lib/python3.5/site-packages/websockets/protocol.py", line 456, in read_message
    frame = yield from self.read_data_frame(max_size=self.max_size)
  File "/home/mike/.local/lib/python3.5/site-packages/websockets/protocol.py", line 511, in read_data_frame
    frame = yield from self.read_frame(max_size)
  File "/home/mike/.local/lib/python3.5/site-packages/websockets/protocol.py", line 546, in read_frame
    self.reader.readexactly, is_masked, max_size=max_size)
  File "/home/mike/.local/lib/python3.5/site-packages/websockets/framing.py", line 86, in read_frame
    data = yield from reader(2)
  File "/usr/lib/python3.5/asyncio/streams.py", line 670, in readexactly
    block = yield from self.read(n)
  File "/usr/lib/python3.5/asyncio/streams.py", line 627, in read
    yield from self._wait_for_data('read')
  File "/usr/lib/python3.5/asyncio/streams.py", line 457, in _wait_for_data
    yield from self._waiter
  File "/usr/lib/python3.5/asyncio/futures.py", line 361, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 662, in _read_ready
    data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer

这个异常是非致命的，程序能够重新连接——我想做的是防止这个异常转储到标准输出并弄乱我的文本界面。

我尝试使用 ensure_future 来处理它，但它似乎不起作用。我错过了什么吗：

@asyncio.coroutine
def handle_exception():
    try:
        yield from WebSocketCommonProtocol.run()
    except Exception:
        print("SocketException-Retrying")


asyncio.ensure_future(handle_exception())
#start discord client
client.run(token)

Answer 1

Task exception was never retrieved - 实际上不是将异常传播到标准输出，而是一条日志消息，警告您您从未在其中一项任务中检索到异常。您可以找到详细信息 here.

我想，在您的情况下避免此消息的最简单方法是手动从任务中检索异常：

coro = WebSocketCommonProtocol.run()  # you don't need any wrapper
task = asyncio.ensure_future(coro)

try:

    #start discord client
    client.run(token)

finally:

     # retrieve exception if any:
    if task.done() and not task.cancelled():
        task.exception()  # this doesn't raise anything, just mark exception retrieved

Answer 2

Mikhail 提供的答案完全可以接受，但我意识到它对我不起作用，因为引发异常的任务深埋在某个模块中，因此尝试检索它的异常很困难。我发现如果我只是为我的 asyncio 循环设置自定义异常处理程序（循环由不和谐的客户端创建）：

def exception_handler(loop,context):
   print("Caught the following exception")
   print(context['message'])

client.loop.set_exception_handler(exception_handler)
client.run(token)

Python3.5 Asyncio - 防止任务异常转储到标准输出？

Python3.5 Asyncio - Preventing task exception from dumping to stdout?

python

python-3.x

python-asyncio

discord.py