Skip to content

Conversation

@hauntsaninja
Copy link
Collaborator

I added tests for this change in #20709 so it's easier to see the diff. Like a few others, this was factored out of #20660 to make that one easier to land.
The change in bytes narrowing is also desirable (but unfortunately only applies with --no-strict-bytes). We can figure out something else for that case, as discussed in #20704

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@hauntsaninja hauntsaninja marked this pull request as draft February 3, 2026 07:51
I added tests for this change in python#20709 so it's easier to see the diff.
Like a few others, this was factored out of python#20660 to make that one
easier to land.
The change in bytes narrowing is also desirable (but unfortunately
only applies with --no-strict-bytes). We can figure out something else
for that case
@hauntsaninja
Copy link
Collaborator Author

hauntsaninja commented Feb 3, 2026

The primer diff + the tests will be fixed by #20728

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

Diff from mypy_primer, showing the effect of this PR on open source code:

schemathesis (https://github.com/schemathesis/schemathesis)
+ src/schemathesis/specs/openapi/extra_data_source.py: note: In member "weighted_select" of class "VariantUsageTracker":
+ src/schemathesis/specs/openapi/extra_data_source.py:85: error: Statement is unreachable  [unreachable]

core (https://github.com/home-assistant/core)
+ homeassistant/components/firefly_iii/sensor.py:190: error: Statement is unreachable  [unreachable]

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.

1 participant