Python 的 raise
和 raise from
之间的区别是什么?html
try: print(1 / 0) except Exception as exc: raise RuntimeError("Something bad happened")
输出:python
Traceback (most recent call last): File "test4.py", line 2, in <module> print(1 / 0) ZeroDivisionError: division by zero During handling of the above exception, another exception occurred: Traceback (most recent call last): File "test4.py", line 4, in <module> raise RuntimeError("Something bad happened") RuntimeError: Something bad happened
而 raise from
:app
try: print(1 / 0) except Exception as exc: raise RuntimeError("Something bad happened") from exc
输出:code
Traceback (most recent call last): File "test4.py", line 2, in <module> print(1 / 0) ZeroDivisionError: division by zero The above exception was the direct cause of the following exception: Traceback (most recent call last): File "test4.py", line 4, in <module> raise RuntimeError("Something bad happened") from exc RuntimeError: Something bad happened
不一样之处在于,from
会为异常对象设置 __cause__
属性代表异常的是由谁直接引发的。htm
处理异常时发生了新的异常,在不使用 from
时更倾向于新异常与正在处理的异常没有关联。而 from
则是能指出新异常是因旧异常直接引发的。这样的异常之间的关联有助于后续对异常的分析和排查。from
语法会有个限制,就是第二个表达式必须是另外一个异常类或实例。对象
若是在异常处理程序或 finally
块中引起异常,默认状况下,异常机制会隐式工做会将先前的异常附加为新异常的 __context__
属性。get
固然,也能够经过 with_traceback()
方法为异常设置上下文 __context__
属性,这也能在 traceback
更好的显示异常信息。it
raise Exception("foo occurred").with_traceback(tracebackobj)
from 还有个特别的用法:raise ... from None
,它经过设置 __suppress_context__
属性指定来明确禁止异常关联:io
try: print(1 / 0) except Exception as exc: raise RuntimeError("Something bad happened") from None
输出:ast
Traceback (most recent call last): File "test4.py", line 4, in <module> raise RuntimeError("Something bad happened") from None RuntimeError: Something bad happened
在异常处理程序或 finally
块中引起异常,Python 会为异常设置上下文,能够手动经过 with_traceback()
设置其上下文,或者经过 from
来指定异常因谁引发的。这些手段都是为了获得更友好的异常回溯信息,打印清晰的异常上下文。若要忽略上下文,则能够经过 raise ... from None
来禁止自动显示异常上下文。