-
-
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
Use MessageBuilder.pretty_callable in more places #5490
Comments
Another thing to note here is that maybe we need to trim horizontally long signatures anyway. Some complex overloads in typeshed can produce huge error messages. |
Increasing priority since I think that we can always use the "native" format for complex callable types. We'd then only use
For everything else we can probably use the more readable The relevant code is in |
#12037 implements this, but needs some conflicts fixed. Anybody want to help with this? |
Hey, @JukkaL , I'm a newby in contributing to Mypy, so correct me if I'm wrong...
And in the
Thank you for your attention!! |
Currently callable types in many error messages are formatted as
We should probably switch to more "native" format that is already used in some errors (e.g. for protocol and overloads):
The main obstacle here is probably updating all tests that use the old format.
This is a follow up for #5463
The text was updated successfully, but these errors were encountered: