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

Fix literal context for ternary expressions (for real) #18545

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

ilevkivskyi
Copy link
Member

I am not waiting for review as the fix is obvious. The only annoying thing is that we had an exact test as in the repro but it passed accidentally because we use builtins fixtures.

Copy link
Contributor

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

@ilevkivskyi ilevkivskyi merged commit 16e19f8 into python:master Jan 27, 2025
18 checks passed
@ilevkivskyi ilevkivskyi deleted the fix-literal-ternary-for-real branch January 27, 2025 10:58
wesleywright pushed a commit that referenced this pull request Jan 27, 2025
I am not waiting for review as the fix is obvious. The only annoying
thing is that we had an exact test as in the repro but it passed
accidentally because we use builtins fixtures.
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