Skip to content

Test case for fixed namedtuple method call #18666

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

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

ilevkivskyi
Copy link
Member

Fixes #15600

The issue was previously "fixed" because of another bug. Now that everything is properly fixed, we can add this "regression" test just in case.

@ilevkivskyi ilevkivskyi merged commit 03cf35c into python:master Feb 12, 2025
12 checks passed
@ilevkivskyi ilevkivskyi deleted the add-nt-any-test branch February 12, 2025 20:05
ericmarkmartin pushed a commit to ericmarkmartin/mypy that referenced this pull request Feb 19, 2025
Fixes python#15600

The issue was previously "fixed" because of another bug. Now that
everything is properly fixed, we can add this "regression" test just in
case.
ericmarkmartin pushed a commit to ericmarkmartin/mypy that referenced this pull request Feb 19, 2025
Fixes python#15600

The issue was previously "fixed" because of another bug. Now that
everything is properly fixed, we can add this "regression" test just in
case.
x612skm pushed a commit to x612skm/mypy-dev that referenced this pull request Feb 24, 2025
Fixes python#15600

The issue was previously "fixed" because of another bug. Now that
everything is properly fixed, we can add this "regression" test just in
case.
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.

False positive about self argument with union of namedtuple and Any
1 participant