Skip to content

Conversation

@cdce8p
Copy link
Collaborator

@cdce8p cdce8p commented Sep 26, 2024

Source commit:
python/typeshed@a94c927

cdce8p and others added 4 commits September 26, 2024 12:09
This is allegedly causing large performance problems, see 13821

typeshed/8231 had zero hits on mypy_primer, so it's not the worst thing
to undo. Patching this in typeshed also feels weird, since there's a
more general soundness issue. If a typevar has a bound or constraint, we
might not want to solve it to a Literal.

If we can confirm the performance regression or fix the unsoundness
within mypy, I might pursue upstreaming this in typeshed.

(Reminder: add this to the sync_typeshed script once merged)
@github-actions
Copy link
Contributor

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

core (https://github.com/home-assistant/core)
- homeassistant/components/knx/config_flow.py:198: error: Argument 1 to "anext" has incompatible type "AsyncGenerator[Any, None] | None"; expected "_SupportsSynchronousAnext[Awaitable[Any]]"  [arg-type]
+ homeassistant/components/knx/config_flow.py:198: error: Argument 1 to "anext" has incompatible type "AsyncGenerator[Any, None] | None"; expected "_SupportsSynchronousAnext[Coroutine[Any, Any, Any]]"  [arg-type]

@JukkaL JukkaL merged commit 7237d55 into python:master Sep 26, 2024
17 of 18 checks passed
@cdce8p cdce8p deleted the sync-typeshed branch September 26, 2024 14:40
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.

4 participants