[1.15 regression] (Temporary) false positive for reachability with unannotated partial type · Issue #18606 · python/mypy · GitHub

Sort of a weird / minor case, but with mypy 1.15

λ cat e.py
def merge_debugs(debugs: list[int | None]) -> None:
    metadata = None
    for debug in debugs:
        if debug is not None:
            if metadata is None:
                metadata = {}

λ mypy  e.py --warn-unreachable
e.py:6: error: Need type annotation for "metadata" (hint: "metadata: dict[<type>, <type>] = ...")  [var-annotated]
e.py:6: error: Statement is unreachable  [unreachable]
Found 2 errors in 1 file (checked 1 source file)

If you add an annotation to metadata (standalone or with the assignment) the unreachable warning goes away

Another example:

y = None
for i in range(5):
    if y is None:
        print('reachable!')  # Mypy: error: Statement is unreachable
        y = []
    y.append(99)

(playground)

Avoid false `unreachable` and `redundant-expr` warnings in loops more…

Avoid false `unreachable`, `redundant-expr`, and `redundant-casts` wa…

[1.15 regression] (Temporary) false positive for reachability with unannotated partial type · Issue #18606 · python/mypy · GitHub

Repository navigation

[1.15 regression] (Temporary) false positive for reachability with unannotated partial type #18606

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

[1.15 regression] (Temporary) false positive for reachability with unannotated partial type · Issue #18606 · python/mypy · GitHub

Repository navigation

[1.15 regression] (Temporary) false positive for reachability with unannotated partial type #18606

Description

Activity

Garrett-R commented on Feb 9, 2025

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions