Skip to content

mypy: fix all call-overload - #367

Merged
jaraco merged 4 commits into
pypa:mainfrom
Avasam:mypy--fix-all-call-overload
Jul 8, 2026
Merged

jaraco merged 4 commits into
pypa:mainfrom
Avasam:mypy--fix-all-call-overload

Conversation

@Avasam

@Avasam Avasam commented May 4, 2025

Copy link
Copy Markdown
Contributor

No description provided.

@Avasam
Avasam force-pushed the mypy--fix-all-call-overload branch from c281d20 to 565f29c Compare May 4, 2025 16:41
@Avasam
Avasam force-pushed the mypy--fix-all-call-overload branch 2 times, most recently from 1fdc63b to 80b7e84 Compare July 4, 2026 19:08
@Avasam
Avasam force-pushed the mypy--fix-all-call-overload branch 2 times, most recently from 1c3c8fa to 3ec9133 Compare July 5, 2026 15:04
@Avasam
Avasam force-pushed the mypy--fix-all-call-overload branch from 3ec9133 to 519a68f Compare July 7, 2026 21:27
jaraco and others added 3 commits July 8, 2026 11:27
The base Compiler is abstract and every concrete subclass supplies its
own compiler_type, so the base has no meaningful value to provide. An
annotation-only declaration keeps the type non-null (str) without the
str/None inconsistency, and makes a subclass that forgets to set it fail
loudly with AttributeError rather than silently returning None.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jaraco
jaraco merged commit 4a80c90 into pypa:main Jul 8, 2026
20 checks passed
@Avasam
Avasam deleted the mypy--fix-all-call-overload branch July 8, 2026 16:04
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