Skip to content

Treat Type[Any] as builtins.type with --strict-equality #7824

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 30, 2019
Merged

Treat Type[Any] as builtins.type with --strict-equality #7824

merged 1 commit into from
Oct 30, 2019

Conversation

@ilevkivskyi
Copy link
Member

@ilevkivskyi ilevkivskyi commented Oct 30, 2019

Fixes #7823

This makes Type[object], Type[Any], and type behave the same way w.r.t. type overlaps.

@ilevkivskyi ilevkivskyi requested a review from JukkaL October 30, 2019 12:54
@ilevkivskyi ilevkivskyi merged commit 92f9429 into python:master Oct 30, 2019
@ilevkivskyi ilevkivskyi deleted the overlap-type-meta branch October 30, 2019 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JukkaL JukkaL JukkaL approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Strict equality false positive with Type[Any]

2 participants

@ilevkivskyi @JukkaL