-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
(🎁) What if unsupported features reported a warning instead of silently(or unexpectedly) failing #12397
Comments
I was trying to implement Concatenate for a while before realizing it was unsupported, since I thought I was simply using it incorrectly. This would be very nice to have! 👍 Another example of a as-yet unsupported feature: Self. This is the current result of using Concatenate, FYI:
The last one is quite, um, interesting. :) |
Related #9531 |
Closing, since we support PEP 612. We'll try to keep in mind for future type system features, e.g. we currently do issue a warning about PEP 695 |
Full
ParamSpec
support is on the way(#8645) but until that time, completely valid usages ofParamSpec
andConcatenate
are met with perplexing error messages that most people would misinterpret as misusing the feature.I believe it would be at least 10 times more understandable if mypy showed a warning in these circumstances:
Proposed behavior:
Idk if it's possible to determine what would constitute a warning, next best thing would be to show the current error with an info message.
The text was updated successfully, but these errors were encountered: