Fix a false positive for redefined-outer-name when there is a nam…

…e defined in an exception-handling block which shares the same name as a local variable that has been defined in a function body.

Closes pylint-dev#9671

doc/whatsnew/fragments/9671.false_positive

@@ -0,0 +1,3 @@
+Fix a false positive for ``redefined-outer-name`` when there is a name defined in an exception-handling block which shares the same name as a local variable that has been defined in a function body.
+
+Closes #9671

pylint/checkers/variables.py

@@ -1520,6 +1520,8 @@ def visit_functiondef(self, node: nodes.FunctionDef) -> None:
                     continue
 
                 line = definition.fromlineno
+                if line > stmt.lineno:
+                    continue
                 if not self._is_name_ignored(stmt, name):
                     self.add_message(
                         "redefined-outer-name", args=(name, line), node=stmt

tests/functional/r/redefined/redefined_except_handler.py

@@ -70,3 +70,18 @@ def func():
     # pylint:disable-next=invalid-name, unused-variable
     except IOError as CustomException:  # [redefined-outer-name]
         pass
+
+
+def function_before():
+    """https://github.com/pylint-dev/pylint/issues/9671
+
+       The local variable `e` should not trigger `redefined-outer-name`
+       when `e` is also defined in the subsequent exception handling block.
+    """
+    e = 42
+    return e
+
+try:
+    raise ValueError('outer')
+except ValueError as e:
+    print(e)