14.9 捕获异常后抛出另外的异常.pdfVIP

14.9 捕获异常后抛出另外的异常 问题 You want to raise an exception in response to catching a different exception , but wantto include information about both exceptions in the traceback . 解决⽅案 To chain exceptions, use the raise from statement instead of a simple raise statement .This will give you information about both errors. For example: def example(): ... try : ... int(N/A ) ... except ValueError as e: ... raise RuntimeError(A parsing error occurred) fro example() raceback (most recent call last): File stdin, line 3, in example ValueError: invalid literal for int() with base 10: N/A The above exception was the direct cause of the following exception: Traceback (most recent call last :File “”, line 1, in File “”, line 5, in example RuntimeError: A parsing error occurred As you can see in the traceback , both exceptions are captured . To catch such an excep-tion , you would use a normal except statement . However , you can look at the causeattribute of the exception object to follow the exception chain should you wish . Forexample:try: example( except RuntimeError as e: print(“It didnt work :”, e if e .cause:print(‘Cause:, e .cause An implicit form of chained exceptions occurs when another exception gets raised in-side an except block . For example: def example2(): ... try : ... int(N/A ) ... except ValueError as e: ... print(Couldnt parse:, err) ... example2() raceback (most recent call last): File stdin, line 3, in example2 ValueError: invalid literal for int() with base 10: N/A During handling of the above exception , another exception occurred: Traceback (most recent call last :File “”, line 1, in File “”, line 5, in example2 NameError: global name ‘err is not defined In this example , you get information about both exceptions, but the interpretation is abit different . In this case , the NameError exception