-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Document or explain "<nothing>" #3030
Comments
I would say a better more explanatory error is a better option. I didn't know what it meant till reading more about it, and I expect many others would be similarly confused. |
Agreed. Though actually the better option still might be to not infer UninhabitedType when there are no constraints on a type variable. (See #3032.) |
I just renamed the issue since |
I'm trying to determine where would be the proper place to document this type. |
These are related to type variables, so somewhere here would be a better location: https://github.com/python/mypy/blob/master/docs/source/generics.rst |
Has there been any progress on this in the past five years? |
Users can now get
<uninhabited>
in error messages when there are no constraints on a type variable. This should either be documented somewhere, or we should use a more self-explanatory string to display the type.The text was updated successfully, but these errors were encountered: