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

Updated conformance test results for mypy 1.10 and pyright 1.1.360. M… #1726

Merged
merged 1 commit into from Apr 24, 2024

Conversation

erictraut
Copy link
Collaborator

…ypy added partial support for TypeAliasType and TypeIs. Pyright fixed a couple of bugs in constructor call evaluation.

…ypy added partial support for TypeAliasType and TypeIs. Pyright fixed a couple of bugs in constructor call evaluation.
@erictraut erictraut marked this pull request as ready for review April 24, 2024 17:00
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@@ -1,28 +1,20 @@
conformant = "Unsupported"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can probably be moved to "Partial".

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered that, but I think it's a stretch to say that mypy supports this feature. It no longer generates errors, but it also doesn't implement the feature in any real way. I think "Unsupported" better captures the current state.

@@ -58,5 +58,4 @@ Line 27: Unexpected errors ['aliases_typealiastype.py:27:17 Undefined attribute
Line 35: Unexpected errors ['aliases_typealiastype.py:35:4 Undefined or invalid type [11]: Annotation `GoodAlias4` is not defined as a type.']
Line 37: Unexpected errors ['aliases_typealiastype.py:37:4 Undefined or invalid type [11]: Annotation `GoodAlias5` is not defined as a type.']
Line 39: Unexpected errors ['aliases_typealiastype.py:39:4 Invalid type [31]: Expression `$local_aliases_typealiastype$GoodAlias5[(int, str, [int, str], *tuple[(int, str, int)])]` is not a valid type.']
Line 49: Unexpected errors ['aliases_typealiastype.py:49:12 Undefined attribute [16]: Module `typing` has no attribute `TypeAliasType`.']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Odd that something changed here, since we're still running the same version of Pyre.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's because I needed to add a new "E?" to the test to accommodate mypy's reporting of circular dependencies between type alias definitions.

@JelleZijlstra JelleZijlstra merged commit c62646f into python:main Apr 24, 2024
5 checks passed
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.

None yet

2 participants