-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Literal
objects misinterpreted within collections / mappings
#7547
Comments
What you're doing here is very atypical. In general, pyright assumes that the |
…o textual format for diagnostic messages) so it better handles special forms like `Literal` or unions when used in a value expression. This partly addresses #7547.
…o textual format for diagnostic messages) so it better handles special forms like `Literal` or unions when used in a value expression. This partly addresses #7547.
…a value expression. This addresses #7547.
I added enough support to make your case work along with some related use cases. Making |
This is addressed in pyright 1.1.364. |
I am writing a library that does some runtime type checking, so I am working with type-objects a lot. I encountered the following:
I realize that this is a very unusual use of
Literal
, and it isn't a big deal for me to just ignore this.The text was updated successfully, but these errors were encountered: