mypy: drive remaining 161 errors on backend/app/ down to 0 (decomposition) #155

New issue

Closed

opened 2026-09-14 22:52:10 +00:00 by Mark · 1 comment

Mark commented

2026-09-14 22:52:10 +00:00

Owner

Residual mypy errors after PEP 695 de-sugar commit on branch fix/retry-handler-pep695.

Counts (from mypy --no-incremental backend/app/):

39 [attr-defined]
20 [no-any-return]
19 [unreachable]
19 [assignment]
16 [union-attr]
10 [index]
8 [str]
8 [redundant-cast]
7 [unused-ignore]
7 [operator]
remainder of 161 across smaller cats

Strategy: incremental bucketing per type. Each commit ~=10 errors. Mechanical clusters go to kilo-gsd-runner. [attr-defined] and [assignment] clusters need domain knowledge — defer until rules exist.

Predecessor branch fix/retry-handler-pep695 (1802c42) handles the PEP 695 type-parameter syntax that mypy 1.13 cannot parse. master is fine for that and any mypy run will then proceed past the syntax error.

Residual mypy errors after PEP 695 de-sugar commit on branch fix/retry-handler-pep695. Counts (from `mypy --no-incremental backend/app/`): - 39 [attr-defined] - 20 [no-any-return] - 19 [unreachable] - 19 [assignment] - 16 [union-attr] - 10 [index] - 8 [str] - 8 [redundant-cast] - 7 [unused-ignore] - 7 [operator] - remainder of 161 across smaller cats Strategy: incremental bucketing per type. Each commit ~=10 errors. Mechanical clusters go to kilo-gsd-runner. [attr-defined] and [assignment] clusters need domain knowledge — defer until rules exist. Predecessor branch fix/retry-handler-pep695 (1802c42) handles the PEP 695 type-parameter syntax that mypy 1.13 cannot parse. master is fine for that and any mypy run will then proceed past the syntax error.