Skip to content

Narrow a minimal-repair curve's grid values for mypy 2.3.0 - #355

Merged
derrynknife merged 1 commit into
devfrom
fix/mypy-interp-0.14
Oct 16, 2026
Merged

derrynknife merged 1 commit into
devfrom
fix/mypy-interp-0.14

Conversation

@derrynknife

Copy link
Copy Markdown
Owner

Summary

CI's lint job failed on the release pull request (#353): mypy 2.3.0, which pyproject.toml pins, reports MinimalRepairCurve.at and events passing an Optional array (up, failures) to np.interp. The arrays are set together with times, which the methods already check; mypy 2.3.0 does not carry that narrowing to them (2.3.1 does, which is why scripts/check.sh passed locally with a newer mypy on the path). Each read now asserts the invariant. No behaviour change.

Reproduced with python -m mypy --python-version 3.11 repyability on mypy 2.3.0 (2 errors), clean after the change; black and flake8 clean; test_minimal_repair_timed.py passes.


Generated by Claude Code

MinimalRepairCurve keeps its grid's values (up, failures) as optional
beside its times, set together. mypy 2.3.0, which CI pins, does not
narrow them with the times at np.interp, and failed the release pull
request (#353); mypy 2.3.1 does. Each read asserts the invariant.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Ng6hwUY8zznhm1jRfZJqZ
@derrynknife
derrynknife merged commit d3950f0 into dev Oct 16, 2026
@derrynknife
derrynknife deleted the fix/mypy-interp-0.14 branch October 16, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants