Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync typeshed #17855

Merged
merged 4 commits into from
Oct 1, 2024
Merged

Sync typeshed #17855

merged 4 commits into from
Oct 1, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 1, 2024

Sync typeshed

Source commit:
python/typeshed@91a58b0

Note that you will need to close and re-open the PR in order to trigger CI.

mypybot and others added 4 commits October 1, 2024 00:06
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)
@hauntsaninja hauntsaninja reopened this Oct 1, 2024
Copy link
Contributor Author

github-actions bot commented Oct 1, 2024

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

@hauntsaninja hauntsaninja merged commit 1855bb9 into master Oct 1, 2024
19 checks passed
@hauntsaninja hauntsaninja deleted the mypybot/sync-typeshed branch October 1, 2024 02:11
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