Question

尽管我最外层的try: / except:总是会捕获一个异常（这可能不是一个好主意，但这是不可能的）：

try:
    try:
        raise ValueError
    except:
        raise ValueError
except:
    pass

在some code中，我要面对的情况是

def process_batch(self):
    try:
        p = util.json_dumps(self.batch_data)
        mac = hmac.new(self.key, p)
        send_bytes = struct.pack('B', mac.digest_size) + mac.digest() + p
        s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
        try:
            try:
                s.connect((self.host, self.port))
            except socket.error:
                s.close()
                s = socket.socket(socket.AF_INET6, socket.SOCK_STREAM)
                s.connect((self.host, self.port))
            s.send(send_bytes)
        finally:
            s.close()
    except Exception:
        self.logger_logger.exception("Failed to send network data")

引发异常：

2019-02-09 23:32:51     INFO (simplemonitor) monitor passed: hass
2019-02-09 23:32:51     INFO (simplemonitor) monitor passed: dns
2019-02-09 23:32:51    ERROR (simplemonitor.logger-send-to-srv) Failed to send network data
Traceback (most recent call last):
  File "/opt/simplemonitor/Loggers/network.py", line 89, in process_batch
    s.connect((self.host, self.port))
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/simplemonitor/Loggers/network.py", line 93, in process_batch
    s.connect((self.host, self.port))
socket.gaierror: [Errno -5] No address associated with hostname

为什么会这样？为什么没有包罗万象的try: / except:捕获异常？

Answer 1

在提供的第二个代码示例中，Traceback消息实际上不是未处理的异常，这是由于异常处理程序调用了logger.exception方法，该方法将打印出指定的消息以及完整的{{ 1}}消息发送到日志记录流。如果不希望使用Traceback，则使用Traceback会产生与logger.error相同级别的日志消息。

为何尝试过多：/例外：不足以捕获异常？

1 个答案: