From 54d03df1e6584ffcf0c8fafd308d4c167efffb53 Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Fri, 25 Mar 2022 05:49:31 -0400 Subject: Don't emit `raising-bad-type` when there is ambiguity (#5968) Co-authored-by: Pierre Sassoulas --- .../invalid_exceptions/invalid_exceptions_raised.py | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'tests/functional') diff --git a/tests/functional/i/invalid/invalid_exceptions/invalid_exceptions_raised.py b/tests/functional/i/invalid/invalid_exceptions/invalid_exceptions_raised.py index 475326545..3b4229741 100644 --- a/tests/functional/i/invalid/invalid_exceptions/invalid_exceptions_raised.py +++ b/tests/functional/i/invalid/invalid_exceptions/invalid_exceptions_raised.py @@ -108,3 +108,21 @@ def reusing_same_name_picks_the_latest_raised_value(): def bad_case10(): """raise string""" raise "string" # [raising-bad-type] + + +class AmbiguousValue: + """Don't emit when there is ambiguity on the node for the exception.""" + def __init__(self): + self.stored_exception = None + + def fail(self): + try: + 1 / 0 + except ZeroDivisionError as zde: + self.stored_exception = zde + + def raise_stored_exception(self): + if self.stored_exception is not None: + exc = self.stored_exception + self.stored_exception = None + raise exc -- cgit v1.2.1